Answered

Using a condition with a terminate action causes the condidion to have no inputs

(0) Share

Report

Posted on by DerekSmith

Hello,

To start, This used to work just fine, but now I have 3 different versions of the same flow that are experience the same problem.

The Problem:

When my flow is run I get the same cancelled flow each and every time, even when it should be working.

Point of occurrence:

The condition checks 2 things:

That the file type being passed in is a PDF
That the vendor I'm looking for exists in a SP list.

(Notice the No inputs in the condition)

If I remove the terminate, and then resubmit the exact same input, the condition works!

However, because the conditions were not met, I want the flow to stop there and not continue.

What happened that caused this to no longer work?

It last ran correctly on January 25, which was the last time I was testing this.

(I've been waiting on another group before I could fully test)

Any help would be much appreciated.

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

DerekSmith 51 on at

Like (0)

Report
Copy link

Link copied!

To elaborate further:

With the terminate action in place, the condition always shows no input.
So even if the condition should be True, there are no inputs and it terminates the flow.

Was this reply helpful? Yes No
VictorIvanidze 13,079 on at

Like (0)

Report
Copy link

Link copied!

Just remove Terminate action and move all remaining actions (Initialize etc) to the left branch "If yes"

Was this reply helpful? Yes No
DerekSmith 51 on at

Like (0)

Report
Copy link

Link copied!

I guess that's an option, but theres ~30-40 steps after this.
And it's not so good for readability with a couple other conditional steps along the way as well.

What I'm really after is why did it stop working correctly, and how to make it work like it did 3 months ago?

Was this reply helpful? Yes No
DerekSmith 51 on at

Like (0)

Report
Copy link

Link copied!

I deleted the condition step and added it back in, with the same result

I then started a new workflow, and rebuilt the first several steps up to this condition.

I get the same problem with the no inputs into the condition if a terminate it present.
Seems like a pretty big bug out there if anyone was using a condition to terminate a flow.

It's disappointing that the changes along the way cause so many issues with existing flows.
I'm getting nervous about putting a full scale solution into production, and how often I will need to implement emergency fixes when things like this change.

Was this reply helpful? Yes No
Verified answer

DerekSmith 51 on at

Like (0)

Report
Copy link

Link copied!
I found a solution that worked on my test flow.
Instead of using Terminate action I used Cancel Flow Run action

Where the expressions are:
workflow().tags.environmentName
workflow().name
workflow().run.name

This lets the condition input flow through and actually work.

Was this reply helpful? Yes No