Incremental models temporarily breaking shortcuts?

[dylanirion]

We have adopted a pattern of doing our ETL with dbt into a warehouse in one workspace, and serving these tables out to lakehouses in other workspaces via shortcuts.

Our analysts occasionally mention hitting errors when querying these shortcuts from the sql endpoints for the lakehouse, e.g. "Failed to complete the command because the underlying location does not exist."

I suspect this is maybe a result of a full-refresh and the table metadata getting momentarily re-created? Has anyone experienced anything similar?

[dylanirion]

Seems to happen on table materializations. The uuid for the parquet file reported in the error appears to be different to the uuid I see in the fabric ui, so perhaps it's a cache thing? Browsing the sql endpoint in the fabric ui also appears to refresh things.

[dylanirion]

https://learn.microsoft.com/en-us/fabric/data-factory/refresh-sql-endpoint-activity

Maybe there is a way to trigger this from dbt cloud? We've set this up in Fabric for the time being.