Flow Designer - Wait for Condition not working

[Community Alums]

I have a flow I'm trying to test and It doesn't appear to be working:

What I have done:
I added a field to the sys_user table called Timer1 (to mimic a day timer which is hard to test for)

I setup a Catalog Item to get as variables the user as a reference - This will allow me to bring it in as something to wait on

I setup the flow with basic things. 
Catalog Trigger
Bring in the Variables
Wait for Condition
Log information

Here is what I'm looking to do.  I have a request to have the flow Start 9 days before start date (which is on the sys_user record.  I was thinking I could just do a Wait for Condition where Timer1 relative before 5 minutes ahead. So the flow would continue 5 minutes before timer1 was set.  Everything looks fine.  At less than 5 minutes before the timer is set to expire the flow continues to set in a waiting state.

 Am I doing something wrong here?  I'm a bit puzzled as to why the condition is not being met and staying in a waiting state.

[Ankur Bawiskar]

@Community Alums 

so basically you need to wait until that date/time is reached?

If yes then check this link where solution is shared, the solution tells how to use system property but you can pick the value from that sys_user field

Using flow designer Wait for duration until reach the Value of system property. 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[vishwajeet5550]

-Go to the Flow Designer and open the flow where the Wait for Condition

-Review the condition you’re waiting for. Ensure that the logic is correct

-If you're using a record condition, ensure that the condition is aligned with the field's value or state.

-Make sure that the value or record you're waiting for will indeed be updated. If the flow is waiting for a record to be created, updated, or deleted, ensure that such actions are happening in the system

-If the condition depends on a delay (like a field update), ensure that the record is updated within the expected timeframe.

-Ensure the trigger conditions are correct and that the flow is activated at the right time

-Verify that the trigger is not set to only fire once or under conditions that prevent it from executing as expected

-Look for the specific flow execution record where the "Wait for Condition" action was executed

-Check the logs for any issues or errors related to the flow’s execution, such as failed conditions, skipped actions, or timeout

Ensure the flow is reaching the Wait for Condition action and it's evaluating the condition properly

-Record locking can prevent the Wait for Condition from being triggered, causing the flow to fail or hang

-If you’re using an advanced condition with a script

-Add gs.info() debug statements in the script to log values and troubleshoot what might be going wrong in the evaluation

-Ensure that the script correctly checks for the expected condition, and that asynchronous or delayed actions are handled properly

-The Wait for Condition action has a timeout setting that specifies how long the flow will wait for the condition

-Review the Timeout value set for the action. If the timeout is too short, increase it to allow more time for the condition to be satisfied

-Confirm that the user or role executing the flow has sufficient permissions to read, write, or modify the records involved in the condition

-If there’s a lack of permissions, the flow might not be able to evaluate or update the condition correctly.

-Ensure that your instance of ServiceNow is up to date. Sometimes issues with Flow Designer actions may arise due to bugs in a particular version

-Check ServiceNow’s Release Notes or Known Issues page for any bugs related to the Wait for Condition action in your version

-If the Wait for Condition is still not working, consider using alternative actions

-Using a Timer with a Condition Check: Instead of waiting for a condition directly, use a timer