Gateway Scheduled refreshing Problem

[mellolu]

Hi everyone, a few months ago my scheduled updates started failing. The gateway and connections are online. If I force the update, it still happens. I don't know what to do anymore. I've uninstalled and updated the gateway, but the problem persists. What can I do to fix this? Help me please!!!!😪

[v-agajavelly]

Hi @mellolu ,

Did you get a chance to check whether the gateway was online during the scheduled refresh window? If you’ve already verified the version and logs but still see the same error, I’d strongly suggest opening a support ticket with Microsoft using the Activity ID/Request ID so they can trace the issue deeper on their side.

Thanks,
Akhil.

[tayloramy]

Hi @mellolu, 

The error messages you are getting point to an issue connecting with the gateway. 

If you run a network port test on the gateway server, does it pass? 

It could be that some ports are open and some are not, so sometimes it fails depending on what endpoint the service decides to use? 

Adjust communication settings for the on-premises data gateway | Microsoft Learn

If the network port test comes back good, I recommend submitting a ticket to Microsoft. They can get more telemetry details from their end to troubleshoot more. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.  

[mellolu]

Good morning, the error is always this; what always changes is the table. But when I do the update manually, without using scheduling, the update happens normally.

Erro de fonte de dados: {"error":{"code":"DM_GWPipeline_Client_GatewayUnreachable","pbi.error":{"code":"DM_GWPipeline_Client_GatewayUnreachable","parameters":{},"details":[],"exceptionCulprit":1}}} Table: empresas_cnaes.<br />Cluster URI: WABI-BRAZIL-SOUTH-redirect.analysis.windows.net<br />ID da atividade: 97c66a82-8e46-41d1-bb5a-f5fe2aa57c0d<br />Solicitar ID: 6a13de35-e6b9-4e86-8dd3-59b73e388674<br />Hora: 2025-09-16 16:32:30Z

[v-agajavelly]

Hi @mellolu ,

Thanks for sharing the details. Since the refresh works manually but fails on schedule with the GatewayUnreachable error, this usually points to a gateway or network reliability issue.

• Confirm the gateway is running the latest version and hasn’t gone offline during scheduled refresh.
• Check if there are any timeouts, throttling, or antivirus/firewall policies that might intermittently block the gateway service.
• Review the gateway logs around the failure timestamp for more clues.

If the problem persists even after verifying these, I’d recommend raising a Microsoft support ticket with the Activity ID and Request ID you shared, that way the product team can trace the failing pipeline run directly.

Thanks,
Akhil.

[tayloramy]

Hi @mellolu, 

This error means the gateway isn't reachable. Can you confirm that the data gateway is online? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.  

[v-agajavelly]

Hi @mellolu ,

Thanks @tayloramy  for the detailed steps.

Just to add the very first thing to do is check the Refresh History (Dataset → Settings → Refresh History). Troubleshoot refresh scenarios - Power BI | Microsoft Learn
The exact error text there will tell us the real cause, otherwise we’re only guessing.

From experience, the most common solutions are.

• Re-enter your data source credentials these often expire or reset without notice. Add or remove a gateway data source - Power BI | Microsoft Learn
• Use UNC paths (\\server\share\file) instead of mapped drives (X:\) if your report uses local/network files.
• Verify your gateway mapping in the Service matches exactly what you used in Desktop (server name, alias, IP, database, file path, etc.). Even a small mismatch can cause refresh failures. On-premises data gateway - Power BI | Microsoft Learn

If you can share the refresh history error message here, we’ll be able to point you to the exact fix.

Regards,
Akhil.

[mellolu]

Hi. Thank you for your support. As you can see, it's an intermittent error. I've already reconnected all the connections, and the gateway is online and running the latest version.

[v-agajavelly]

Hi @mellolu ,

Thanks for sharing the screenshots, that really helps. The error message (DM_GWPipeline_Client_GatewayUnreachable) means the Power BI Service can’t consistently connect to your on-premises gateway. Since you already confirmed. That gateway is online and updated and Connections have been remapped and credentials re-entered.

This points to a network or environment issue. Some things to check that.

• The gateway server is always on and not going to sleep/restarting during refresh.
• Firewall/proxy rules allow outbound ports 443, 5671–5672, 9350–9354.
• Gateway region matches your tenant (your error shows Brazil South).

Since the error is intermittent, the most common fix is firewall or proxy configuration not allowing the Service Bus traffic through consistently. If your IT/network team can confirm the above ports are open and not being throttled, it should resolve.

If after this the issue continues, I’d recommend raising a Microsoft support ticket so they can trace the failing refresh ID in their backend.
Create support ticket: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks,
Akhil.

[v-agajavelly]

Hi @mellolu ,

Just checking in were you able to verify the gateway ports and network/firewall settings as suggested? If the issue persists, raising a Microsoft support ticket with the failing refresh ID usually helps resolve these intermittent connectivity errors. Let us know how it goes so we can assist further if needed.

Thanks,
Akhil.

[tayloramy]

Hi @mellolu, 

What error messages are you getting when the refresh fail? This will help us determine the root cause. 

Here's some steps to troubleshoot: 

1) Get the exact error: In the dataset’s settings, open Refresh history and copy the latest failure text. It points to the real cause and helps avoid guessing. Microsoft doc
2) Rebind to the gateway: In Settings > Gateway connection, pick the correct gateway and map every data source. Server, database, and file paths must match exactly what your queries use. If Desktop used an IP or a different server alias, create the same on the gateway data source or update the queries. Microsoft doc
3) Re-enter credentials: In Settings > Data source credentials, sign in again for each source. This is the most common fix after password or token changes. Microsoft doc
4) Update the gateway: Install the latest gateway on the server and restart the Windows service. Old builds can break after security changes. Microsoft doc
5) Use UNC paths for files: If your model uses files or folders, change mapped drives like X:\ to a UNC path like \\server\share\folder in both Desktop and the gateway data source. Radacad guide
6) Fix privacy levels: If you combine sources, set all privacy levels consistently (usually Organizational) in Desktop and in the Service. This resolves the “Information is needed in order to combine data” failures. Microsoft doc
7) Network and TLS: Ensure outbound ports are open (443, 5671–5672, 9350–9354) and the box uses modern TLS. Proxies can also block Service Bus traffic. Microsoft doc
😎 Region alignment: The gateway’s region should match your tenant/environment. If it doesn’t, reinstall and pick the right region. Microsoft doc

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[mellolu]

Hi. Thank you for your support. As you can see, it's an intermittent error. I've already reconnected all the connections, and the gateway is online and running the latest version.