Forum Discussion
Power BI Service stopped refreshing reports despite online gateway and SQL Server connection
Hi everyone,
I'm facing a critical issue with Power BI Service. Suddenly, all of my scheduled report refreshes stopped working. The day before everything was running perfectly, but the next day, almost every dataset started failing—even though the on-premises data gateway is online and updated to the latest version.
What’s confusing is that a few reports still manage to refresh, but the vast majority are stuck for hours before eventually failing. This happens regardless of whether the dataset is large or small. All of them use a SQL Server connection.
Here are some example errors:
Data source error: The request was cancelled because the connection was closed. Table: Contas a Pagar.
Cluster URI: WABI-BRAZIL-SOUTH-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 6813f312-36e1-42b7-a1c8-54035ac3ab8d
Request ID: f3ace3d9-8a9c-5073-1ffd-24a68e349240
Time: 2025-07-08 18:35:57Z
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}}
Table: dim_faturamento.
Processing error: An internal service error occurred, causing the cancellation of previous refresh attempts. New attempts will now be initiated.
Data source error: The request was cancelled because the connection was closed.
I’ve already checked:
The gateway is online and running the latest version.
The SQL Server is accessible and responsive.
Some reports do succeed, but most just hang and fail after hours.
Has anyone else experienced this recently? Any guidance or ideas would be greatly appreciated.
Thanks in advance!
With assistance from Microsoft support, an issue was identified in the internal network, and after reviewing the rules, the updates resumed successfully.
6 Replies
Thank you for reaching out to the Microsoft Fabric Forum Community.
anilelmastasi rohit1991 Thanks for the inputs.
The suggestions they provided are very helpful. Additionally, please check the CPU, memory, and network usage on the machine running the gateway during refresh times. If the system is experiencing heavy load, it may cause delays or refresh timeouts.
If you continue to experience issues after trying all the suggestions above, please contact us. We are happy to assist you.
Thanks.I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.
With assistance from Microsoft support, an issue was identified in the internal network, and after reviewing the rules, the updates resumed successfully.
- anilelmastasi
Super User
Hello ihavequestionto ,
Errors like "DM_GWPipeline_Gateway_TimeoutError" and “request was cancelled because the connection was closed” typically indicate that the gateway is terminating the query—often after ~10 minutes due to gateway or SQL command timeout settings.
Could you please try this in your M code:
Source = Sql.Database(
"your_server",
"your_db",
[
CommandTimeout=#duration(0,2,0,0),
ConnectionTimeout=#duration(0,2,0,0)
]
) 
rohit1991This problem is most likely caused by a hidden issue with your on-premises data gateway or network connection, even if everything looks onlin, common causes include the gateway service being unhealthy, SQL Server connectivity interruptions, too many concurrent refreshes, or problems introduced by recent updates.
To fix it:
-
Restart your gateway service and check for Windows or network issues.
-
Stagger your dataset refresh schedules to avoid overloading the gateway or SQL Server.
-
Review the gateway and Power BI logs for any errors or timeouts.
-
If possible, test using a different gateway machine.
-
If the issue persists, contact Microsoft support and provide your refresh error Activity
-
