Should I use AND or Or for Wait condition? Workflow stuck in waiting when fields aren't emtpy.

[jaubert]

I created a flow and it seems to be stuck in waiting after my conditions are met, and I just need a second eye.  I have attached a copy of the condition, which I am expecting it to continue running after it has been met. Is there a way I can troubleshoot and see what is returned during execution? 

[Kieran Anson · Accepted solution]

Hey, The following is from the docs which is likely why you're not seeing the wait for condition progressing

Restrict wait conditions to fields present on the current tableThe Wait For Condition action can only monitor changes to the fields of the table to which the record belongs. The action cannot detect changes to fields in related records or catalog variables. For example, if an action waits for changes to an Incident record, then it cannot detect changes to a related record such as a catalog item or change task record. Avoid building wait conditions that dot-walk to another record as these fields actually belong to the related record. Avoid building wait conditions that rely on catalog variables.

Wait For Condition action (servicenow.com)

Rather than using a wait for condition, generate a task and wait for that to be closed. You can se the variables to be mandatory on this task to prevent it being progressed until information is provided

[jaubert]

Thank you so much for the information!