Microsoft Issue - Refreshes Getting Stuck unable to cancel

[JSanders28]

We are an enterprise Power BI Premium customer with 4 Power BI Premium Capacities.  We have been experiencing issues over the past week where datasets will get stuck refreshing and we are unable to cancel.  It says "canceling".  We've tried rebooting the gateways, switching capacities,  but refreshes are stuck. Can't even manually refresh in PBI desktop and publish over.  Yes we're on a supported version of the on-premise data gateway.  We opened a Microsoft ticket, just posting to see, is anyone else experiencing this?  

[Dunners]

Exactly the same issue here: manual refresh happens in seconds but anything scheduled seems to get stuck and cannot cancel it

[JSanders28]

We have the issue happening again! It's happening more frequently where we can't cancel refreshes. (Including yesterday for several high impact refreshes). @Dunners just curious are you still seeing the same issue

[nithinbhandary]

Facing the same issue with our premium capacities. Datasets get stuck in the “canceling” state, and we are unable to manually refresh or republish from Power BI Desktop. We have already tried restarting the on-premises data gateways and moving workloads between capacities, but the issue still persists.

[jbpbi]

This issue happening again, it seems we can't cancel refreshes even if gateway rebooted.

[KilianM]

Does anyone have an alternative solution to temporarily contain this issue? It appears that we will need to wait for Microsoft to investigate, but there is currently no ETA provided.

[danisrael8]

Anyone find a realistic solution for this? For a premium capacity the only thing I can do is wait for the report to time out (5 hours). This is crazy for a report that takes 3 minutes to normally refresh. Outside of deleting the semantic model and republishing, I haven't found anyway around this wait time. This is unrealistic as a lot of our semantic models are linked to multiple reports downstream, deleting and republishing would take way too long to fix all the downstream reports. XMLA and Rest API cancel commands only act like hitting the online "cancel" button, so no change there.