Error - Cannot load model - Direct Lake Semantic Model

[KJarvis]

Hello,

We've started building PBI reports off a Direct Lake semantic model and we've notice users occasionally getting a "Cannot Load Model" error when they view the report:

The error does seem to resolve itself as they can just close the error message and view the report with up to date data. So it's more of an annoyance.  I've noticed the last refresh on the model will match when the error pops up like the view triggers a model refresh.

Is there anything we can do to prevent the error from popping up?  This error does seem to pop up in any or our reports using a direct lake model and is not isolated to a specific model.  The Lakehouses do use shortcuts to warehouse tables. 

[v-abhinavmu]

Hi @KJarvis,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. 

Thank you.

[KJarvis]

We have submitted a ticket with microsoft for support.  We are still waiting to see if they can figure out the issue.

Also note all the model refreshes have the same issue.  First refresh fails with the same "we cannot process the request right now.  One lake security has changed error."  Followed by another successful request a few seconds later.

But a successful model refresh only temporarily resolves the issue.  Viewers still get the error pop-up when viewing the report throughout the day.

[GilbertQ]

Hi @KJarvis 

I would double check with your workspace administrator or your OneLake security administrator to see if any changes were made unknown to you which could be causing this error to pop up from time to time.

[tayloramy]

Hi @KJarvis, 

Every time OneLake Security changes, the DirectLake models need to be refreshed.  Refreshing the model should resolve the error. 

[KJarvis]

Do you know what could be causing OneLake Security to change?  Refreshing data in the warehouse?  But that seems to automatically trigger a direct lake refresh on the model.  We aren't making any changes to permissions.

The user viewing the report seems to trigger a refresh which resolves the error.  But we want to avoid users getting the error message.