New Instance of flow not starting

[Sree Gorantla1]

Hi,

We have below steps in Flow and trigger is Stage changes to 'Draft' on a Custom table.

Step 1 Stage is 'Draft'

Step 2 Stage is 'Manager approval'

Step 3 Stage is 'VP Approval'

So if at step 2 or 3 it is rejected I set the Flow Stage back to 'Draft' (for doing the corrections and send to approval again) and end flow. I am expecting a new instance of flow starts as Trigger condition matched but it is giving attached error. Any advise on how to deal with this scenario?

"Failed to run flow trigger for trigger runner: 2ad8e8968721c25042fc975e3fbb350f of class: class com.glide.flow_trigger.engine.RecordTriggerRunner on record: " 

[James Chun]

Thanks, looks like the system is trying to prevent recursion of flows.

In the following article - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0830765

it states that 'Flow Designer ignores any request to start a flow that is the result of direct recursion.........An action or subflow produces a result matching the flow trigger. For example, a flow that runs when an incident record is updated contains an update record action that updates an incident record.'

I have tried something similar in my PDI and can confirm it behaves the same as yours.

Instead of the Flow triggering itself again, it needs to be triggered by a different source.

One solution I can think of is, set the value of the 'stage' to a different value (e.g. Draft) with the Flow and create a UI Action for a user to click which would change the 'stage' to 'requestor entry'. The Flow trigger would remain the same but it will be initiated by users.

Hope that helps, cheers

[Sree Gorantla1]

Thanks! I will give it a try.

[Sumanth16]

Hi @Sree Gorantla1 ,

Please refer to below thread:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0997550

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[Sree Gorantla1]

@Sumanth16 I have issue only for this flow, looks like this KB is for different issue. Thanks!