Flow did not terminate and I can't cancel it

(0) Share

Report

Posted on by SL-21111327-0

I have two different flows for two lists in SharePoint set up almost identical. If we receive a response, the flow should terminate immediately. Otherwise, it moves on to the parallel branch and checks for responses and sends reminder emails.

Example of it working correctly:

However, today I see all the runs that show as Succeded and show the terminated action completed successfully but the counter is still active on the parallel branch. We do not want those reminder emails going out because they have already responded. The cancel button is grayed out on all of these runs.

What would have caused this and how else can this be cancelled?

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Pstork1 68,888 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The fact that its a parallel branch and not a branch based on a condition means it will always run. When doing an approval with reminders you need to put some kind of a check in the reminder branch to finish it up when the approval is completed. Please Note: that any delays you put in the reminder side will still need to finish before the branch completes. So for this kind of flow I normally use a counter with an outer and inner loop in the reminder. The inner loop has a short duration. That way when the approval is complete I can max out the counter so it checks for the completion of the approval after the next loop.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

1 people found this reply helpful.

Was this reply helpful? Yes No
SL-21111327-0 5 on at

Like (0)

Report
Copy link

Link copied!

Thanks Paul! That makes sense. Looks like the parallel branch finally got cancelled. Just took about an hour before that happened. I've never noticed it takes one hour to cancel that branch once a response is received, but upon reviewing my first screenshot there and then a few of my other successful runs in my other flow, it seems that's how it has always worked (it just takes an hr for some reason). I appreciate your response though. Definitely some good insights to have when setting up these type of flows.

Was this reply helpful? Yes No