Forum Discussion
Semantic Model Refresh Failure
Hello IAMCS
We’re seeing this quite frequently: Fabric pipelines failing at the final semantic model refresh step. The native Semantic model refresh activity works in simple cases but is fragile in real‑world usage, particularly where there are concurrent refresh attempts, OAuth token instability with user accounts, or tight capacity constraints. As the activity wraps the Power BI REST API and polls for completion, any collision or transient issue often causes the pipeline to fail even though the model refreshes successfully when run manually.
For more reliable behaviour, many teams are calling the Power BI REST API directly via a Web activity, using a service principal and explicit polling logic. The commonly used endpoint is:
POST https://api.powerbi.com/v1.0/myorg/groups/{groupId}/datasets/{datasetId}/refreshes
This pattern allows better handling of “refresh already in progress” scenarios, clearer error reporting, and controlled retries. In enterprise environments with multiple pipelines or schedules, it has proven significantly more robust than relying solely on the built‑in activity.An earliest post on this issue can be found here -
Solved: Re: Semantic Model Refresh not working in Data Pip... - Microsoft Fabric Community
Hello IAMCS
We’re seeing this quite frequently: Fabric pipelines failing at the final semantic model refresh step. The native Semantic model refresh activity works in simple cases but is fragile in real‑world usage, particularly where there are concurrent refresh attempts, OAuth token instability with user accounts, or tight capacity constraints. As the activity wraps the Power BI REST API and polls for completion, any collision or transient issue often causes the pipeline to fail even though the model refreshes successfully when run manually.
For more reliable behaviour, many teams are calling the Power BI REST API directly via a Web activity, using a service principal and explicit polling logic. The commonly used endpoint is:
POST https://api.powerbi.com/v1.0/myorg/groups/{groupId}/datasets/{datasetId}/refreshes
This pattern allows better handling of “refresh already in progress” scenarios, clearer error reporting, and controlled retries. In enterprise environments with multiple pipelines or schedules, it has proven significantly more robust than relying solely on the built‑in activity.
An earliest post on this issue can be found here -
Solved: Re: Semantic Model Refresh not working in Data Pip... - Microsoft Fabric Community