Forum Discussion
Automatic refresh error
Hi Matheus_R ,
This issue is quite common and is often due to temporary service interruptions or minor cloud connection problems. Since you’ve already checked your credentials and setup, it’s a good idea to wait a bit and try refreshing again, as these errors sometimes resolve on their own. In the meantime, review the refresh history in Power BI Service for any authentication or connector issues, and attempt a manual refresh in Power BI Desktop to see if the issue is related to the service schedule or the dataset. Make sure your Google Sheet is shared correctly for Power BI access, and if you use an on-premises gateway, verify that it’s online and functioning properly.
Refer these Microsoft Documentations for reference :
Microsoft: Troubleshoot Refresh Scenarios
Microsoft: Refresh Data in Power BI Desktop
Microsoft: Configure and Manage On-premises Data GatewayHope this helps if you have any queries we are happy to assist you further.
Regards,
Sreeteja.
Hi Matheus_R
This type of error usually indicates that the scheduled or on-demand refresh process for your semantic model failed due to issues related to connectivity, authentication, or capacity availability rather than a specific problem in the model itself. Since the Cluster URI shows WABI-BRAZIL-SOUTH-B-PRIMARY, it means the model is hosted in the Brazil South region, and the Activity ID and Request ID are generated for Microsoft support tracking. Common causes include expired or missing credentials for one of the data sources, an on-premises data gateway being offline or misconfigured, insufficient capacity (especially on shared or overloaded Premium capacity), or network/firewall rules blocking the refresh process. Another possibility is that you’re using DirectQuery or mixed-mode sources that require gateway access, and the refresh is trying to validate or pre-fetch schema information but fails due to authentication issues.
To troubleshoot, go to Power BI Service → Dataset/Semantic Model → Settings → Data source credentials, and make sure all credentials are valid and show no errors. If a gateway is involved, ensure it’s online and mapped correctly to each data source. Check the Refresh history of the dataset to see the detailed error message for the failed refresh, as this often gives more insight than the brief error summary. If you’re using Premium capacity, review capacity metrics to ensure refreshes aren’t being throttled. If everything seems correct but the error persists, you can use the Activity ID to raise a support ticket with Microsoft, as they can trace the backend failure more precisely.