Answered

Condition comparing two variables hangs when outcome is true

(0) Share

Report

Posted on by IanWallbridge

Hi all,

I have a Flow that manages the upload of documents into a SP library, and up until a week ago, it was working fine. It's now developed an issue whereby a condition that compares two variables will hang - and eventually time out - if the condition is true. If the condition is false, the flow continues correctly.

I have tried exporting and re-importing the flow, and have also recreated a new version from scratch, but I'm unable to either fix the problem or understand why it has suddenly starting failing. Can anyone help?

The basic flow is:

Overall flow.jpg

and the condition is:

All advice welcome!

Thanks,

Ian

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

ChristianAbata 8,953 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

please @IanWa try to see if you don't have some blank space I recoomend you to use the expression trim('HERE YOUR VARIABLE') and test 😉

Was this reply helpful? Yes No
abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @IanWa

It shouldn't hang in conditions for comparing two values. Just to debug further try hardcode two values (expected when it hangs) under the variables and see that works or not.

Thanks

Was this reply helpful? Yes No
Verified answer

efialttes 14,756 on at

Like (1)

Report
Copy link

Link copied!

Hi!

So your Condition evaluation still works fine, and it gets stuck inside the True (yes) branch, right?

If so, can you share a screenshot from your current flow 'True branch' design? Please also expand all True branch action blocks (just doubleclick on its names) so we can see their inputs

Thanx!

Was this reply helpful? Yes No
IanWall 7 on at

Like (0)

Report
Copy link

Link copied!

Thanks everyone for your input, all of which helped me to think this through.
What I'd not realised is that - unlike many other types of flow step - 'condition' will only show as complete in run history when a dependant action is successful, NOT just when the condition has evaluated. I'd assumed that because run history stopped at the condition, the fault was with the condition, when it was actually much further down.
Definitely a learning curve...

Was this reply helpful? Yes No
efialttes 14,756 on at

Like (0)

Report
Copy link

Link copied!

@IanWall @IanWa

Issue solved finally?

If so, CONGRATS!

Was this reply helpful? Yes No