flow runs stuck canceling after batch "Cancel all flow runs"

[DJorgensen-XRM]

I have 3 different flow that had some instances in the "Running" state. Less than 100 combined "running" items. I used the "Cancel all flow runs" button in make.powerapps.com, where it said it may take several seconds, up to several hours, to cancel running flows depending on how many of them there are. Several hours later, all the flow instances are stuck in the "Canceling" state. Even if it was taking 1 minute per cancel, it should have been done by now. Plus I would have expected to see SOME of the items with status "Cancelled" as they were cancelled but this obviously isn't the case. 

Th problem - it looks like having the flows stuck canceling is blocking the flow from triggering (trigger is a row created in a dataverse table).  I can manually "test run" the flow, but the trigger itself doesn't fire when items are created. I've tried turning flows off and back on, etc, but flow still doesn't trigger.

Any suggestions how to fix the problem?

[sammysword]

Did you get a solution to this? My flows have been cancelling for around an hour and none of them have moved to cancelled yet.

[DJorgensen-XRM]

No solution. I still have flows "canceling" after 48 hours.

[ErikOehrtman]

I'm having the same issue, my flow hung (suddenly jumped from taking ~20 seconds to process to taking hours).  Since clicking the cancel all flows button, I have ~15 flows waiting and 5 in canceled status for 45+ minutes.  I have concurrency control set to 5 to avoid throttling issues.

[DJorgensen-XRM]

I see some of my "cancelling" flows have moved to "Cancelled" state. Not all, but some, after 72 hours.

[sammysword]

Mine were the same. After 24 hours I maybe had 5-10% of mine change to cancelled instead of cancelling. I eventually gave up and recreated the flow and deleted the old one. 

[PaulCS]

I've had two runs stuck in "Canceling" for over three days. This is ridiculous. I am growing fonder of unix by the day ("kill -9 1234" worked. Immediately.)

I wound up copying the flow to a -v2 so I could make changes and continue testing without worrying what those zombie flows were doing. 

Anyone have any ideas? 

Will it let me delete the flow? 

[mac_witos]

I had this issue. My Flow stuck in the 'Cancelling' stage for 24h. I found the solution to force the Flow and move it to the 'Cancelled'.

1. Create new Flow.
2. Use Activity 'Cancel Flow Run'. You can find this activity in 'Power Automate Management' connector activities. 
3. Select Environment > Flow > and provide Run ID of the Flow that you want to Cancel. You can find it in URL when you open this Flow Run. For example: 
https://make.powerautomate.com/environments/<your env ID>/flows/<your flow ID>/runs/<your run ID>
4. Run the Flow.
5. The flow should be cancelled.

I hope it will help. 🙂

[AmyF]

I cannot find the activity you mention nor power automate management... do I need to be an admin to do this?  I'm the sharepoint list owner and the flow owner.    Can you elaborate.  Also I see no dates on this thread, I can't tell if it's old or new.  I see things like "Monday" in it but no anchoring date reference.

[DJorgensen-XRM]

That would only allow cancelling 1 flow instance at a time, correct? Considering we're here because we used the bulk delete, creating hundreds if not thousands, of canceling flows, a bit more work in the flow example would be good, to first get all the canceling flows and iterating over those to cancel. Thanks for the idea

[jerome_almir]

Following @mac2 suggested solution, here's what I did to batch-cancel my stuck flows:

1. Go to your Flow Run History
2. Get .csv file

3. Filter CSV by Run Status

4. Copy all Run ID

5. Transform Run IDs to an array format. Ex:
["RunID1", "RunID2"]

1. Create a manual trigger flow

2. Add 'Initialize a variable' action

3. Make sure Type = Array

4. Paste Run ID array in Value

5. Add 'Apply to Each' action

6. Select output from previous Initialize Variable action

7. Add action 'Cancel Flow Run' by Power Automate Management (search for "flow" then find the Cancel Flow Run from the list of actions)
8. Select your Environment

9. Select your Flow

10. Choose Apply to Each -> Current Item as the Run ID

11. Run your flow. It might take a bit to cancel all stuck flows but it will definitely do the trick.