Forum Discussion
Dataflow - timeout after 10 minutes
- 1 year ago
Hi ganiu_,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to GilbertQ, Royel, for those inputs on this thread.
The issue you are experiencing is due to a known limitation in Power BI Dataflows, where query execution is limited to a maximum of 10 minutes in the Power Query Online environment. Since your SQL query takes approximately 13 minutes, it exceeds this limit and results in a timeout. Dataflows Limitations, restrictions and supported connectors and features - Power BI | Microsoft Learn
Power Query Online Usage Limits - Power Query | Microsoft LearnOptimize Your SQL Query: Try reducing execution time using filtering, indexing, or pre-aggregated views. This might help bring the processing time under the 10-minute cap.
Dataflows best practices - Power BI | Microsoft Learn
Use a Staging Table: Load your 1.66M row query into a staging table via SQL Server Agent or automation. Then, point your Dataflow to the already populated staging table, which loads faster. This approach helps avoid timeout errors by removing heavy query logic from the Dataflow refresh process.Use Power BI Desktop Instead: If Dataflows aren’t mandatory for your scenario, you can load the full dataset in Power BI Desktop (which doesn’t have a 10-minute timeout). Then publish the report and use scheduled refresh via gateway, if needed. Data refresh in Power BI - Power BI | Microsoft Learn
Using incremental refresh with dataflows - Power Query | Microsoft Learn
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.
Hi ganiu_,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to GilbertQ, Royel, for those inputs on this thread.
The issue you are experiencing is due to a known limitation in Power BI Dataflows, where query execution is limited to a maximum of 10 minutes in the Power Query Online environment. Since your SQL query takes approximately 13 minutes, it exceeds this limit and results in a timeout. Dataflows Limitations, restrictions and supported connectors and features - Power BI | Microsoft Learn
Power Query Online Usage Limits - Power Query | Microsoft Learn
Optimize Your SQL Query: Try reducing execution time using filtering, indexing, or pre-aggregated views. This might help bring the processing time under the 10-minute cap.
Dataflows best practices - Power BI | Microsoft Learn
Use a Staging Table: Load your 1.66M row query into a staging table via SQL Server Agent or automation. Then, point your Dataflow to the already populated staging table, which loads faster. This approach helps avoid timeout errors by removing heavy query logic from the Dataflow refresh process.
Use Power BI Desktop Instead: If Dataflows aren’t mandatory for your scenario, you can load the full dataset in Power BI Desktop (which doesn’t have a 10-minute timeout). Then publish the report and use scheduled refresh via gateway, if needed. Data refresh in Power BI - Power BI | Microsoft Learn
Using incremental refresh with dataflows - Power Query | Microsoft Learn
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.