Workflow stuck at Wait for Condition activity on RITM state change

ashutoshkum
Tera Contributor

4 weeks ago

Hello Everyone,
I am facing an issue with a workflow on the sc_req_item table.
In my workflow, there is a Wait for Condition activity which waits for the RITM state to become In Progress.
• The activity condition is: State=2
• I have confirmed in the dictionary that In Progress = 2.
• I have also verified the table (sc_req_item) and the state values are correct.
• Still, the workflow remains stuck at the Wait activity, even though the RITM state is updated to In Progress.
• The workflow only moves forward when I update the RITM with some other field change (like adding a comment).
What I have already tried:
1. Added a Timer (3 seconds) before the Wait for Condition activity (as suggested by ServiceNow support), but the issue persists.
2. Modified the Wait script to answer = (current.state == 2); explicitly.
3. Verified dictionary value of “In Progress” is 2.
4. Confirmed that state is changing correctly on the record (saw in history).
5. Deactivated custom Business Rules to ensure they are not blocking updates — no luck.
6. Even created an If Condition before Wait to validate the state, and it shows that the state is In Progress, but the Wait for Condition doesn’t recognize it.
Observation:
When I assign the RITM (update Assigned to), the state automatically changes to In Progress — but workflow doesn’t wake up.
It only wakes when another update (like “Additional Comments”) is made.
Question:
• Has anyone else faced this issue with Wait for Condition on sc_req_item?
• Do I need to check request_state instead of state in the Wait activity?
• Or is there a better approach (like Event / Flow Designer) to handle this?
Any guidance will be appreciated

0 Helpfuls
  • 370 Views
3 REPLIES 3

Harshal Aditya
Mega Sage
Mega Sage

3 weeks ago

Hi @ashutoshkum ,

 

Good Day!!
Please confirm if the workflow is getting stuck in all the cases or this is happening for one ticket only.
Did you tried nudging the workflow ?

Open the workflow context record, there you will find button to Nudge the workflow.

Please let me know if it works

0 Helpfuls

Sharique Azim
Mega Sage

3 weeks ago

Probably the direct solution is to have a run script at the start of the workflow , atleast before wait for condition like simply current.update(); 

However your wait for condition may be wrongly configured too, if possible provide the script and also some screenshots to understand better for us to debug.

 

Lastly, try to create another wait for condition activity block  with same condition and map it to the correct path, so that we can rule out the chances of the block being corrupted in some form.

0 Helpfuls