Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Is anyone getting below error while refreshing reports on Services:
Reports are working fine on desktop.
Solved! Go to Solution.
That is standard behavior when your capacity admin has set query timeouts.
You can assume that in general the service is strict when it comes to enforcing timeouts, while the desktop relies on the data sources to enforce that.
Hi @anmolmalviya05 ,
Thank you @lbendlin for your response.
You are right, this error also occurs due to query timeouts.
Models hosted on Power BI Pro have a refresh time limit of two hours.
This time limit applies to the duration allowed for refreshing the data and updating the model with the latest information. While sufficient for many scenarios, this time constraint may pose limitations for larger datasets or more frequent refresh requirements
Models hosted on Premium capacities enjoy a more generous refresh time limit of five hours. Premium capacities offer enhanced performance and scalability, allowing for larger datasets and more complex refresh operations.
I just wanted to follow up and check if the issue has been successfully resolved or if you still need further assistance. If you have any remaining questions or require additional support, please don't hesitate to reach out, I’ll be more than happy to assist you further.
Thank you again for your patience, and I look forward to your response.
Best regards,
Chaithra E.
Hi @anmolmalviya05 ,
Thank you @lbendlin for your response.
You are right, this error also occurs due to query timeouts.
Models hosted on Power BI Pro have a refresh time limit of two hours.
This time limit applies to the duration allowed for refreshing the data and updating the model with the latest information. While sufficient for many scenarios, this time constraint may pose limitations for larger datasets or more frequent refresh requirements
Models hosted on Premium capacities enjoy a more generous refresh time limit of five hours. Premium capacities offer enhanced performance and scalability, allowing for larger datasets and more complex refresh operations.
I just wanted to follow up and check if the issue has been successfully resolved or if you still need further assistance. If you have any remaining questions or require additional support, please don't hesitate to reach out, I’ll be more than happy to assist you further.
Thank you again for your patience, and I look forward to your response.
Best regards,
Chaithra E.
Hi @anmolmalviya05 ,
We would like to confirm if you've successfully resolved this issue or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.
The limit for semantic models is 5 hours and for Dataflows it is 24 hours. Definitely not 2 hours.
Hi @anmolmalviya05 ,
The error DM_GWPipeline_Gateway_AdoNetProviderExecuteQueryTimeoutError indicates a query timeout via the On-premises Data Gateway in Power BI Service. While Power BI Pro allows up to 2 hours for refresh, timeouts can still occur due to:
Large datasets, inefficient queries, or network/gateway issues
Firewall restrictions or HTTPS mode enabled in the gateway, try disabling it.
Resource bottlenecks (CPU/memory) on the gateway or data source server.
Try these troubleshooting steps:
Check gateway logs and firewall settings
Ensure HTTPS mode is off in the gateway app
Update the gateway and verify it's running smoothly
Run the query directly on the source to test performance
Optimize data model and enable incremental refresh if possible
Increase timeout settings in both PBIX and gateway config
Schedule refreshes during off-peak hours.
Hope this helps.
Best Regards,
Chaithra E.
That is standard behavior when your capacity admin has set query timeouts.
You can assume that in general the service is strict when it comes to enforcing timeouts, while the desktop relies on the data sources to enforce that.
User | Count |
---|---|
32 | |
17 | |
11 | |
9 | |
8 |
User | Count |
---|---|
51 | |
31 | |
24 | |
17 | |
15 |