Forum Discussion
Direct Lake Model Outages
Issue: Direct Lake semantic model randomly locks out tables, showing credential or column access errors.
Not Caused By: Capacity limits, access issues, refreshes, ETL, or query load.Likely Causes:
- Silent fallback to DirectQuery due to unsupported features or metadata drift.
- Delta table schema changes or stale metadata.
- Workspace sync or permission misalignment.
- Backend Fabric service instability.
Fixes:
- Refresh metadata manually (Tabular Editor/Semantic Link).
- Monitor query mode with DAX Studio.
- Align lakehouse and semantic model workspaces.
- Consider logging a Microsoft support ticket.The issue here is a bug that causes the SQL Analytics Endpoint to become out of sync with the semantic model. This can be resolved by refreshing the metadata in the SQL Endpoint. Microsoft is aware of the issue and has an ETA of mid-November for a fix to be released. They have not revealed what specifically causes the two to become out of sync.
Issue: Direct Lake semantic model randomly locks out tables, showing credential or column access errors.
Not Caused By: Capacity limits, access issues, refreshes, ETL, or query load.
Likely Causes:
- Silent fallback to DirectQuery due to unsupported features or metadata drift.
- Delta table schema changes or stale metadata.
- Workspace sync or permission misalignment.
- Backend Fabric service instability.
Fixes:
- Refresh metadata manually (Tabular Editor/Semantic Link).
- Monitor query mode with DAX Studio.
- Align lakehouse and semantic model workspaces.
- Consider logging a Microsoft support ticket.
Thank you Shahid12523. I will move forward with opening a support ticket as all the other fixes you have proposed are items I have looked into.