Unanswered

Control - Terminate does not end the flow

(0) Share

Report

Posted on by plessor88

I have a flow that triggers when an item in a sharepoint list is created or modified.

I built in a control to terminate the flow if a particular field in the item does not contains a certain value. I only want the flow when a particular value is present.

I run the flow and the flow analyzer shows that the condition was activated and that all the subsequent actions were cancelled. Somehow the flow still executes all the actions anyway even though it tells me that it did not do them. For instance I receive emails that should not have been sent because the flow was terminated. I have the analyser screenshot below. Am I fundamentally not understanding how this works or is there some kind of bug here?

As you can see, the subsequent tasks show as "skipped", but they were not skipped, they executed all the steps including sending emails, creating tasks, etc. (there are a lot more stops that I did not upload and all of them show as "skipped")

Any Help is appreciated.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Dorul 340 on at

Like (0)

Report

Hi @plessor88
I didnt try it myself, because i needed a yes or no branch and my actions would continue from there, but i bet thats the problem in your flow.
Try adding new actions in the No branch, considering you want to terminate the flow on Yes branch.
Something like that: (just edited your printscreen)

Was this reply helpful? Yes No
v-yamao-msft on at

Like (0)

Report

Hi @plessor88,

Do you want to terminate the flow if a field doesn’t contain a certain value? If it doesn’t contain the certain value, terminate the flow, if it contains the certain value, then do the following actions.

From the screenshot, it seems that you didn’t add any actions under the If no branch.

I have made a simple flow for testing, when an item is created/modified in a list, if the Title doesn’t contain “test”, terminate the flow, if no, send an email. It works as expected.

Besides, here is a blog could be your reference:

https://veenstra.me.uk/2018/09/11/microsoft-flow-never-terminate-your-flows-unless-you-like-failure/

Best regards,

Mabel

Was this reply helpful? Yes No
Verified answer

plessor88 21 on at

Like (0)

Report

I figured out what the issue was.

My flow is based on a trigger for sharepoint "When an item is created or modified".
Several steps into the flow, I modify that trigger item.
This kicks the flow off again.
I have logic in the flow to terminate this second flow immediately.
The flow analyzer tool lags a bit behind what is actually happening.
I was looking at the trace from the second run of the flow, where all actions are cancelled.
I needed to look at the trace from the first run of the flow, which executed all the actions.
Because the two run within seconds of each other, the analyzer tool was difficult to understand.

I feel pretty dumb, but glad I went through the steps to understand what was happening.

Was this reply helpful? Yes No