The issue is now resolved and fixed on the next release of ArcGIS Pro 2.9. There were some initial issues related to this functionality in ArcGIS Pro 2.7 and 2.8, but the issue has been addressed. Please let us know if the issue persist with specific workflows.