Allow updating live flows without removing customers currently in progress
N
Norhan Eid from SleekFlow
Currently, when changes are made to a live flow and the flow is republished, customers who are already in progress are removed from the flow logs and effectively dropped from the active journey.
This creates major operational challenges for teams that frequently optimize and iterate on flows.
To avoid disrupting active customers, teams must:
- Duplicate the live flow.
- Apply changes in the duplicated version.
- Activate the new flow.
- Keep the old flow active until all customers finish the journey.
- Manually deactivate the old flow afterwards
Since many teams continuously improve flows (copy changes, timing tweaks, messaging adjustments, logic optimization), this workaround creates significant overhead and complexity.
It also results in:
- fragmented analytics across multiple duplicate flows.
- difficulty tracking true performance of a single journey.
- increased risk of errors when maintaining multiple versions.
- reduced confidence in scaling automation.
They want:
Safe publish mode to:
- Publish updates without resetting current enrollments.
- Preserve flow progress for contacts already mid-journey.
This is particularly important for teams actively optimizing conversion journeys and AI-assisted flows on an ongoing basis.
M
Mia Zheng from SleekFlow
Merged in a post:
Preserve Active Enrollments When a Flow Is Edited
N
Naomi Cheung
When a workflow is updated, users can avoid interrupting contacts who are already mid-journey, reducing unexpected cancellations and disruption.