Automatic refresh error

[Matheus_R]

Hello. I'm trying to setup automatics refreshes on my demantic models, but I always get the same error:

• Cluster URIWABI-BRAZIL-SOUTH-B-PRIMARY-redirect.analysis.windows.net
• Activity ID0f0e46ef-ee52-4c6c-9b62-7e239e6aaa82
• Request ID6595da2e-4c08-4aa7-83e7-7182ec4a3af8
• Time2025-10-06 18:21:46Z

Any idea of it it may be and what may solve this issue?

Thank you!

[v-sshirivolu · Accepted solution]

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 Gateway

Hope this helps if you have any queries we are  happy to assist you further.

Regards,
Sreeteja.

[v-sshirivolu]

Hi @Matheus_R ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

[v-sshirivolu]

Hi @Matheus_R ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[Poojara_D12]

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.

[Shubham_rai955]

"The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support."

This indicates the refresh failure was due to an internal service error on the Microsoft Fabric/Power BI backend, often temporary in nature. The best course of action is to retry the refresh after some time. If the problem persists, contacting Microsoft support would be recommended to investigate underlying service issues.

In addition to retrying later, verify credentials and gateway status as discussed previously, to rule out external causes from your environment that might coincide with the service error.

[SamsonTruong]

Hi @Matheus_R ,

At what point is this error occurring? Is it occurring when applying the scheduled refresh, or is it occuring during the triggered refresh of the model?

If occuring during the triggered refresh of the model? Can you please navigate to the semantic model refresh history and click into the failed refresh? This should provide a more detailed error message.

The current error in your post only showcases the metadata of the run, and not the error itself.

[Matheus_R]

My refresh history is this. The error occurs when the automatic refresh tries to trigger.
Already went to check data source credentials and importing data with parameters like PubID and SheetGid and always get the same error...

[danextian]

Are you able to refresh from Desktop?

[Matheus_R]

Yes, I am. I refresh daily via Power BI desktop daily since this problem started, a couple weeks ago...

[SamsonTruong]

Hi @Matheus_R , I wanted to check-in to see if you were still facing this error. Similar to what @v-sshirivolu, this error indicates an issue that is generally transient and may be due to temporary service issues. In the past, I've had this error auto-resolve after some time. Are you still encountering the same error?