why Wait for condition cancelled in workflow

Saif Al-Bashiti · ‎06-19-2019

Hello expert!

I have a simple workflow , (WAIT FOR CONDITION ) If ( x > y ) >> then wait to be ( x < y )

but the WAIT FOR CONDITION turn to cancelld ! why that ? please save my day

Saif Al-Bashiti · ‎06-29-2019

After hard week , I have solve this issue by adding a timer for 3 second before " Wait for condition "

I found this tip in SNOW doc :

" Note: A Wait for condition activity should only be used to wait for an external event such as a record update, and not one from a workflow setting a value. If you have a workflow setting a value and want to wait for that same field to be seen as 'changed,' try inserting a one-second timer. "

ref : https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/administer/workflow-activities/reference/r_WaitForCondition.html

View solution in original post

Steven Parker · ‎06-19-2019

I can't see the condition of your Wait For, but if I had to guess....that Wait For is looking for the state of the RITM, not the Approval (unless you've scripted it that way). So it's cancelling because "Returned" isn't an RITM state.

Post a screenshot of the actual "Wait for condition" details

Please mark this response as correct and/or helpful if it assisted you with your question.
Steven

Saif Al-Bashiti · ‎06-19-2019

my wait condition , when state == returned

and yes the state for RITM NOT APPROVAL

how i can solve this issue please ? I READ ABOUT A BUG , like a busnisse rule ?

https://community.servicenow.com/community?id=community_question&sys_id=b6629b61db101fc01dcaf3231f96...

Elijah Aromola · ‎06-19-2019

To set it for the request you would need to change the condition builder. Related fields -> request -> request.state =4.

Saif Al-Bashiti · ‎06-19-2019

thanks for your response

still i have this problem , please i need any solution

joshuamayes · ‎06-19-2019

Hey.. calm down man.

Did you look at the business rule that he mentioned in that post you linked?

https://community.servicenow.com/community?id=community_question&sys_id=b6629b61db101fc01dcaf3231f96...

It's likely that your table is running this business rule and triggering the cancellation of workflows.

Change the condition of the business rule to exclude your table and voila!