Flow Designer – What Happens to RITMs After Flow Updates

[Erica2]

Hello,

I would like to better understand how Flow Designer behaves when a flow is updated. For example, suppose Flow Designer created an RITM on 12/22/25, but the associated tasks are not scheduled to be created until 12/30/25 because a Wait for Condition is configured.

If a change is made to the exiting flow, and the updated version is migrated to overwrite the original, what happens to the RITM that was triggered by the old flow?  

Will the flow execution stop entirely, or will it continue to create the associated tasks once the scheduled wait condition is satisfied?

Thank you

[srinija_itom · Accepted solution]

Hi @Erica2 , 

Your flow will execute based on the old flow logic for tasks/requests created  prior to the update.

All the new requests will use new flow logic.

Regards,

srinija 

[Erica2]

Hi @srinija_itom 

You were the first to respond to my question, so I will mark your response as the accepted solution. However, do I need to deactivate the existing flow before updating to the new version? 

Thank you for helping. 

[Hemanth M1]

Hi @Erica2 ,

Not required, go to the flow, update, save, publish, move this through update sets to other instance

[srinija_itom]

Hi @Erica2 , 

Thank you for accepting my solution. Appreciate it. If the update is to the same flow with same sys_id then no need to deactivate old version. It will automatically take the latest update as the newest version. 

sys id of the flow can be found in the url after sysId%3D

Regards, 

Srinija

ServiceNow Rising Star 2025