Flow designer doesn't trigger when record is updated in change_request table.

Akhilesh Kande1
Tera Contributor

‎08-16-2023 04:02 AM

Flow designer doesn't trigger when record is updated in change_request table. Flow trigger conditions are (created or updated) and state is new.

 

- Flow is executing only when change record is created.

- Flow is not executing when change record is updated. (when the record is updated it should cancel the existing flow and create a new flow : Functionality is working fine in Test Instance but not working in Dev Instance)

- Also, Changed the "Run trigger" on the flow to "Only if not currently running" and every option available in that list, still not working.

 

Can any one help me with the resolution.

 

Thanks in Advance!

 

Best Regards,

Akhilesh Kandepu

 

 

0 Helpfuls
  • 2,895 Views
2 REPLIES 2

Community Alums
Not applicable

‎08-16-2023 04:22 AM

Hi @Akhilesh Kande1 ,

Please share your flow designer trigger please.

 

0 Helpfuls

SwarnadeepNandy
Mega Sage

‎08-16-2023 04:25 AM

Hello @Akhilesh Kande1,

There are a few possible causes and solutions for this problem

  • One cause could be that the flow trigger conditions are not set up correctly. You need to make sure that the trigger conditions match the fields and values that are updated in the change_request table. For example, if you want the flow to trigger when the state changes from new to approved, you need to set the trigger condition as state changes from new to approved. You can use the Flow trigger conditions - Product Documentation: Rome - ServiceNow article as a reference for setting up trigger conditions.
  • Another cause could be that the flow has been moved by an update set that has not contained all the trigger mapping that is necessary for the flow to run. You need to verify that the trigger mapping is set up correctly in both the test and dev instances. You can use the Flows are not Triggering when the Condition is met - ServiceNow article as a guide for checking and fixing the trigger mapping.
  • A third cause could be that there is a delay or a backlog in processing the events in the event queue that trigger the flow. You need to check the event queue and see if there are any errors or performance issues that prevent the flow from running. You can use the Issue with the Flow designer not getting/delay in triggering - ServiceNow article as a guide for troubleshooting the event queue.

I hope these suggestions help you resolve your issue 

 

Kind Regards,

Swarnadeep Nandy

0 Helpfuls