Answered

Flows stuck in waiting because a second trigger was added

(0) Share

Report

Posted on by MitchellSpence

Is there a way to cancel flows that are stuck in 'waiting'?

A second trigger was added into the flow, concurrency control was set to 1, now whenever the first trigger is triggered the flow is put into 'waiting'. I turned it off to stop more coming in and deleted the second trigger, but I can't figure out how to delete the flows that are stuck...

It doesn't allow me to update the concurrency controls due to there being active instances of the flow still stuck, throwing code: 'CannotDisableTriggerConcurrency'

Is there a way to delete these stuck instances, or do I need to create a copy and just delete this one?

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (1)

trice602 15,402 Super User 2025 Season 2 on at

Like (1)

Report

I've seen this before - if I remember correctly, click on 'All Runs' in the top right which will allow you to individually select runs (in your case the ones in waiting or stuck status) and then do a bulk cancel. This will not be grayed out if they are waiting, queued, or running.

If that works for you, I'm collecting thumbs up and solution badges - always glad to help! Tom

Was this reply helpful? Yes No
MitchellSpence 22 on at

Like (0)

Report

Hey Tom,
I tried this out, but the button is still greyed out for me.
I tried it with a different flow and the button does work, just not for this case.
I think the second trigger did something and crashed it, or put it into some kind of uncancellable state.

Was this reply helpful? Yes No
trice602 15,402 Super User 2025 Season 2 on at

Like (0)

Report

Understood. I remember when there was a service outage, I had a group of flows stuck in queued status and I I couldn't cancel. Are you able to run this flow now and it is successful? If so, these will eventually disappear and I don't think they are actually waiting.

Was this reply helpful? Yes No
MitchellSpence 22 on at

Like (1)

Report

Unfortunately, I had concurrency control on and set to 1 at a time, so the new flows are all stuck waiting as well.
It doesn't let me change the concurrency control because those waiting flows are all still active.
I'm going to wait until Monday, but if they don't disappear by then I'll just copy it all over to a new flow.

Was this reply helpful? Yes No
Verified answer

trice602 15,402 Super User 2025 Season 2 on at

Like (1)

Report

I would proceed with copying this to a new flow then. Let me know if I can help! Always glad to help! Tom

Was this reply helpful? Yes No