Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hello, since this today, i have many errors with my different dataflows that i cannot explain.
Some are in Timeout
Error detail:
Error: Internal error Request ID: 2dc89190-eccc-4712-9e62-738b80df1e5d Activity ID: 00000000-0000-0000-0000-000000000000 |
And some are just failed
Error detail (same):
Error: Internal error Request ID: 2dc89190-eccc-4712-9e62-738b80df1e5d Activity ID: 00000000-0000-0000-0000-000000000000 |
I didn't had anny problem with those dataflow before that, nothing was change in our Microsot 365.
I have 2 kind of dataflow connection, some are just excel sheet connected trhought Sharepoint connetion, some are pgSQL connection.
Am i the only one in that case ?
Thanks in advance
Solved! Go to Solution.
Hi @Anonymous ,
According to your description, here is my suggestion.
There are two timeout thresholds for Power BI Pro dataflows:
1, two hours at the individual entity level
2, three hours at the entire dataflow level
Please check that if you have too large or too many tables.
And you can consider optimizing your dataflow queries, and consider using query folding on your source systems.
What’s more, you can consider upgrading to Premium Per User, which is not subject to three time-outs and offers increased performance due to many Power BI Premium Per User features.
Regarding the refresh failure, check whether the dataflow connected with SQL has a correct gateway connection which can be used normally.
If it still doesn’t work, try reconfiguring the scheduled refresh.
Please refer to the following documents.
Understanding and optimizing dataflows refresh - Power BI | Microsoft Learn
Best Regards,
Community Support Team _ xiaosun
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous ,
According to your description, here is my suggestion.
There are two timeout thresholds for Power BI Pro dataflows:
1, two hours at the individual entity level
2, three hours at the entire dataflow level
Please check that if you have too large or too many tables.
And you can consider optimizing your dataflow queries, and consider using query folding on your source systems.
What’s more, you can consider upgrading to Premium Per User, which is not subject to three time-outs and offers increased performance due to many Power BI Premium Per User features.
Regarding the refresh failure, check whether the dataflow connected with SQL has a correct gateway connection which can be used normally.
If it still doesn’t work, try reconfiguring the scheduled refresh.
Please refer to the following documents.
Understanding and optimizing dataflows refresh - Power BI | Microsoft Learn
Best Regards,
Community Support Team _ xiaosun
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.