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

[kaushal_snow]

@Erica2 ,

Flow designer does not cancel or stop already running flow instances just because you update the flow definition or migrate a new version.....so if you had a flow that triggered on a ritm on 12/22/25 and it hit a wait for condition that didn’t complete until 12/30/25......the old running instance of that flow will generally continue executing to completion using the logic that was in place when it started...... meaning it will wait for the condition and continue creating associated tasks once the condition is satisfied......and won’t automatically stop or revert just because you deployed an updated version of the same flow.........this behavior happens because snow keeps a runtime execution context for each flow run and updates to the flow definition only apply to new runs triggered after activation of the new version rather than actively running instances........

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Hemanth M1]

Hi @Erica2 ,

This is similar to workflows - once the flow triggers, it will run in the same context. If you update the flow directly, it will only reflect on the net new RITMs that get created.

However, if the flow has a Custom Action or Custom Subflow and you update it, the new version will be used while running the context.

In your case, it will not stop any execution, it will continue to create tasks once the scheduled wait time is over (as per your older logic).

Some thing like this :

Hope this helps!

[Ankur Bawiskar]

@Erica2 

Since your RITM already has a running flow it will use old flow context only.

After you migrate your new flow if new RITM is created then it will get attached with new flow context

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[AndersBGS]

Hi @Erica2 ,

as the RITM has already been triggered, it will use the old flow and not the updated version.

[Shaik Dimple]

Hi @Erica2 

Once a flow is triggered for an RITM, it continues to run using the flow version that was active at the time. Any updates to the flow apply only to new RITMs, not one already inProgress. After the wait for Condition is met, the original flow should continue and create the tasks.

You can usually confirm this by checking the flow context record which retains the flow version tied to that execution.