Flow condition states cancelled no inputs despite value being present in trigger

[Digital]

I have a Flow with a condition that references a boolean value from the trigger outputs (LegalEscalationRequired).

A few recent runs are displaying as Cancelled. The condition says Cancelled No inputs but when I check the output of the trigger condition the value is present.

Does anyone have any idea why this could be happening and how to prevent it happening in the future?

[wskinnermctc]

This is a total guess speculation:

I was looking at something about boolean from sharepoint like a week ago, and it seems like if there is a value like true/yes it is 1.

However, if there is a false/no value, it looks like it is 0, but it's more like null or blank.

Like we couldn't filter on Column eq 0 

We could filter on Column ne 1

I don't know exactly what is going on because it looks one way then behaves another, but I think boolean has a tricky format.

Can you tell if your flow is cancelled on Yes as well as No? Or is it just Cancelled on the No?

[Digital]

Hi @wskinnermctc ,

Thank you for your reply.

Both of the cancelled flows are when the value used in the condition is set to true. The trigger is Cognitio fom submission.

I noticed that the condition was set to If LegalEscalationRequired equals true with true being typed in rather than the true value being added in the dynamic content. I've changed this now but I don't know if that would be an issue because that condition has been evaluating correctly for a while.

[wskinnermctc]

Yeah the expression true vs typed true in a condition is always strange for me. 

Usually the true expression doesn't work and the typed true does. 

Maybe have to wrap the LegalEscalation in a boolean expression?

Or stick it in a boolean variable first then put the variable in the condition?

[grantjenkins]

@Digital If you're having problems with your trigger condition, then I'd suggest creating a Compose action (that you can delete afterwards) and building up the condition in there, where you can also use your dynamic properties to ensure the field names are correct. Then go into Peek code and copy the condition and paste it into your trigger condition. I often go with this approach if my trigger conditions aren't working as expected.

[Digital · Accepted solution]

There was a Try-Catch further down the flow with a Terminate action in the Catch block. I found this was the reason for the flow showing cancelled. This confused me because it was showing cancelled not at the point it was actually cancelled but much further up in the Flow.

[HFG]

I had the same issue and you made me realise the problem was nothing to do with the condition, it was another part of the flow that had an problem but wasn't obvious (number being passed as string in a switch). Thank you !