Forum Discussion
Direct Lake Semantic Model not showing latest data
- 4 months ago
Hi A454A ,
Your understanding is largely accurate, and your explanation reflects how this functions in Fabric. When using Direct Lake with a Warehouse, it still relies on the SQL analytics endpoint, which can introduce a brief delay before new data becomes visible. While this delay is typically minimal, it can vary based on workload, data volume, and update frequency.
You are also correct regarding semantic model refreshes. In Direct Lake mode, a refresh primarily updates metadata rather than performing a full data reload as Import mode does, so new data may not be immediately available if the backend has not yet synchronized. Clearing the report cache does not affect this, as the delay occurs before the semantic model receives the data.
The distinction you mentioned is important. When accessing Delta tables directly without the SQL endpoint, data generally appears much faster. The behavior you're observing is specific to scenarios involving Warehouses or SQL endpoints.
Thank you.
Hi A454A,
Is this DIrectLake On OneLake, or DIrectLake on SQL?
If it is DirectLake on SQL (created from the lakehouse UI) then it needs to wait for the SQL endpoint to refresh, which is not instant. There is a new activity in pipelines to force this refresh.
Hi this is direct lake on Fabric Warehouse!