Flow is stuck at Wait for condition

[SSA1]

Hi,

I have a issue where flow is stuck at wait for condition, my scenario is,

When agent selects ' Can this be remotely done' variable value  as 'Yes' Or "No', then the rest of the flow should execute.

But sometimes flow stuck at this step even though agent has selected Yes or No as a value.

But sometimes it works.

I have tried out enable timeout option but I observe that if agent doesn't selects any value even it will pass this step and execute rest of the flow activitie.

Without that , Is there any other way I can resolve this issue.

(what I want is, If agent hasn't selected any value for this ' Can this be remotely done' variable, It should remain at wait for condition in flow.

otherwise(If any value is selected for ' Can this be remotely done' variable, it should run the other activities in the flow.)

Appreciate any advise / guidance on this

[Matthew Knight]

Apologies I was assuming this was within Workflow editor.

This all looks fine.  What happens when you perform a test execution?

The only other thing I can think of is if there is a method to update the variable from some other means i.e. a script etc that is setting the value of the variable to something different.

I have seen this before when a script could set the value to "no" rather than "No" or even "No " with null values/spaces.

[SSA1]

No this value is manually selected by agent, No any involvement of a script for the updating of this variable. So how can i resolve this appreciate your help

[Matthew Knight]

Hi SSA,

What is the default value of the variable?

When you check the executions on the times it failed what does it say for that step?

It might tell you if the flow was affected by another means or what the run time value is against that variable.

[SSA1]

Here run time value there's a variable called state that's empty

[Matthew Knight]

Ok so I tried to replicate this based on the information provided and found the following.

If I create a variable on the Requested Item called "can_this_be_done_remotely" and set this to a Yes/No with None as the default.

When creating the flow triggered from this I can add the step to get the variables:

When setting up the Wait for Condition we don't have access to this variable as the condition is looking for a field value:

So not sure if you actually just have this configured as a field on the sc_req_item table rather than as a variable