04-22-2024 10:06 AM
@BrianJ - Have shared the details with the Databricks Engineering team to have this issue addressed. we assure that the issue will be prioritized and fixed in the next release. Kindly use the workaround to proceed further on this.
