Forum Discussion
Timeout error when refreshing semantic model connected to dataverse
Hi shimgarah ,
Since the issue started recently and used to work fine before, it may be tied to backend performance changes, query complexity, or API throttling on the Dataverse side.Could you please try the following steps :
-
Review Query Folding
-
In Power Query, right-click a query step and choose "View Native Query" if this option is greyed out, your query isn’t folding, which can severely impact performance.
-
Try moving filters, column removals, and joins as early as possible in the query to encourage folding.
-
-
Split Large Tables
-
If one table is the bottleneck, try splitting it into two queries (e.g., current year + historical), and import them separately. You can merge or append them later if needed.
-
-
Use Incremental Refresh (If on Premium/Pro + Service)
-
Set up incremental refresh so that Power BI only loads changed data rather than reloading everything every time.
-
-
Monitor Dataverse Limits
-
Dataverse enforces API call limits and performance throttling.
-
Try monitoring request load through Power Platform Admin Center, or reduce the refresh frequency temporarily.
-
-
Use Dataflows (Optional)
-
Consider offloading the load process by using Power BI Dataflows to stage your Dataverse data, then connect your semantic model to that instead.
-
-
Thank you all for your responses. The issue hasn't been resolved, but for now, I'm applying an incremental load that creates daily records in the table and updates those that have changed within the past year. However, if I want to modify any part of the design in Power BI Desktop, I will do so using only the initial data and will need to increase the duration of the initial load.
To implement the incremental load, I used the following tutorials:
- Tutorial 1: https://www.youtube.com/watch?v=yvUNDJo6uIs&t=1015s
- Tutorial 2: https://www.youtube.com/watch?v=0vbxtT4D--Y&t=28s
- Microsoft Learn resources: Actualización incremental de los modelos semánticos en Power BI - Power BI | Microsoft Learn
Community SupportHi shimgarah ,
Thank you for reaching out to the Microsoft Community Forum.
Hi rohit1991 , Poojara_D12 , lbendlin Thank you for your prompt response.
Hi shimgarah , in addition to rohit1991 , Poojara_D12 response, I am adding some more points and Microsoft document for troubleshooting.
As you mentioned that, the refresh process which previously completed in about 10 minutes, now fails after around 40 minutes with the below error.
"Microsoft SQL: The timeout period elapsed prior to completion of the operation or the server is not responding".
This typically occurs during the loading of one or more specific tables from Dataverse.
Please refer below workarounds.
1. Update and scale out the on-premises data gateway.
2. Optimize the SQL queries for efficiency.
3. Remove unused columns/tables and avoid complex calculated columns.
4. Increase the SQL timeout in Power Query connection settings.
5. Clear the cache, restarting database service and gateway, and reload the problematic table it resolved the issue.
Please refer Microsoft official document.
Troubleshoot refresh scenarios - Power BI | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
- v-dineshya
Hi shimgarah ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.And, if you have any further query do let us know.
Regards,
Dinesh