Forum Discussion
Advocate IISemantic Model: Error on refresh and not gracefully
Update on this. We have implemented a solution that is working for anyone else struggling with this.
With the help of some very talented engineers, we impletmented a custom dbt materialization method that no longer drops and creates tables on refresh. Ever since that change, we haven't had any errors with the semantic model refresh.
This adds to the suspision that fabric has some bugs with how it handles the parque file relationships.
I'll mark this as the solution. Happy coding everyone.
Community SupportHi NoDice ,
Thanks for reaching out to the Microsoft fabric community forum.
Once try the below workarounds:
- Implement retry logic with backoff instead of fixed delays.
- Test with a custom semantic model for more refresh control.
- Optionally, disable auto-refresh and trigger manually via pipeline.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team
Advocate IIThis seems to be an underlying issue of how Direct Lake mode works specifically when referencing a Warehouse. When a table is dropped and recreated, the semantic model occassionally appears to lose the reference for the current Parquet file, which then makes the model inaccessible.
The only way I have found to remedy this is to:
- Drop the table that is creating the error.
- Recreate the table.
- Update the model via the edit tables button in the Edit Semantic Model UI.
This is a long-standing bug that pops up with Direct Lake models that reference a warehouse. It seems that Microsoft internally can either not reproduce the bug, or does not have the will to resolve it. It is also frustrating that there appears to be no way to programmatically call the process equivalent to using the Edit Tables menu in the UI.