Direct lake mode disabled for power bi report

[LeenaB]

I have a power bi report created on a semantic model (not default) in a fabric workspace. The data in the model has been populated by a pipeline - several jobs add tables. There was an error in one of the tables, hence I deleted the table from the lakehouse and re-ran the job. I then refreshed the semanti model - the data is now correct and refresh is succesful. However I received an email that the Automatic update of the direct lake data has been disabled - direct lake for the semantic model in the workspace - due to retry failure - power bi will no longer detect changes in the data in OneLake. - how can I fix this? what could I have done wrong? My report is heavy and I do not want to rebuild it on a newer semantic model? Any help will be appreciated.

[v-kaiyue-msft]

Hi @LeenaB ,

Thank you @johnbasha33  for your replies and allow me to provide another insight:

By default, data changes in OneLake are automatically reflected in the Direct Lake model. This behaviour can be changed by disabling Keep Direct Lake data up to date in the model settings.

However, Power BI can pause the automatic update of Direct Lake tables if an unrecoverable error is encountered during a refresh, so make sure that the semantic model can be successfully refreshed. Power BI automatically resumes automatic updates when subsequent user-invoked refreshes complete without errors.

More detailed information can be found in the documentation: Learn about Direct Lake in Power BI and Microsoft Fabric - Microsoft Fabric | Microsoft Learn.

If your Current Period does not refer to this, please clarify in a follow-up reply.

Best Regards,

Clara Gong

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[johnbasha33]

@LeenaB 

This issue might have been triggered by the retry failure during the refresh process. Here are steps you can take to troubleshoot and resolve this issue:

1. Check Retry Failure Details: Review the details of the retry failure to understand the root cause. The error message or logs should provide more information about why the automatic update was disabled. This will help you identify the specific issue that needs to be addressed.

2. Verify Data Source Configuration: Ensure that the data source configuration for your Power BI semantic model is correctly set up to access and refresh data from the lakehouse. Check the connection settings, credentials, and any other relevant configurations to make sure they are accurate and up-to-date.

3. Retry the Refresh: Try manually refreshing the semantic model again to see if the issue persists. Sometimes, retrying the refresh process can resolve transient errors or issues that occurred during the previous attempt.

4. Review Workspace Settings: Check the settings of your fabric workspace in Power BI to see if there are any configurations related to automatic updates or data refresh that need to be adjusted. Make sure that automatic updates are enabled and configured correctly for your semantic model.

5. Contact Support: If you're unable to resolve the issue on your own, consider reaching out to Microsoft support for assistance. They can help investigate the issue further and provide guidance on resolving it.
   
   Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!

[LeenaB]

Thanks for the reply - when I check the details - it tells me that it cannot find a direct lake table(several infact). These are the ones that I deleted and regenerated by running the pipeline again. All other settings seem to be fine. Pls note this was working before I deleted the tables. Several manual refresh have noo effect. The refresh option in settings remains disabled by Microsoft. Pls note that if I create a new semantic model I am able to view the changed data, but the earlier report which is built on the earlier semantic model - that has a broken connection with the live data and cannot be refreshed.