Forum Discussion
Report Refresh Failures
Thanks @vivien57 @Shahid12523 Anonymous and @danextian for the valuable inputs here.
I've identified the root cause of the failure; it was due to a service interruption that occurred on September 3rd. That disruption directly led to the issue we experienced.
If there's a service interruption or issue with the Power BI cloud service, you can monitor its status by visiting the support page Microsoft Fabric service status . This support page provides real-time updates and helps identify any ongoing disruptions.Thank you all for your support and patience while I investigated. Much appreciated!
Hi mjoseph111 ,
Thanks vivien57 Shahid12523 and danextian for the valuable inputs here.
As per my knowledge , I just want to add that the refresh failures you’re seeing.
(DM_GWPipeline_Gateway_DataSourceAccessError) are generally tied to capacity strain on P1 in the Gov cloud. The suggestions already shared (staggering refresh times, using incremental refresh, optimizing Power Query/M models, and monitoring via Premium Capacity Metrics App) are the recommended approaches to reduce these errors.
mjoseph111 did you already try staggering your refresh schedule and/or enabling incremental refresh on the larger models? That usually provides the most immediate relief in environments where scaling up (e.g. moving from P1 → higher capacity) isn’t an option.
If these don’t help, then unfortunately there isn’t a separate “fix” specific to sovereign cloud beyond optimization and capacity management, since the service operates with those constraints.
Regards,
Akhil.
Thanks for your response. Refresh intervals are already distributed.