DATE:
AUTHOR:
The Fountain team
Onboarding

Flow Version Rollout Options in Onboard

DATE:
AUTHOR: The Fountain team

Choose who a new onboarding flow version applies to when you publish changes.

Flow Versions let admins update a live flow without duplicating it, but a published change only ever reached workers who had not started yet. When an update needed to apply to workers already moving through the flow, or to workers who had finished, there was no clean way to do it.


What's new

  • Three release strategies — When you publish changes, choose Progressive, In-progress workers, or Apply to all Workers.

  • Progressive — The recommended and safest option, and the behavior you have today. Updates apply only to new workers added to the flow.

  • In-progress workers — Updates apply to everyone who has not yet completed the flow, including workers in an error or failed state. Workers who already finished are left unchanged. The option shows how many workers are currently in progress before you choose it.

  • Apply to all Workers — Updates apply to every worker, including those who already completed the flow. Completing workers have the flow reopened so the change reaches them.

  • A named version with a description — Give each release a version name and an optional description. The version a worker is on appears in the worker list, so you can see at a glance who is on what.

  • Impact confirmed before anything changes — Publishing to everyone shows a breakdown of how many in-progress and completed workers are affected, and asks you to confirm before continuing.


Why it matters

Admins can match the rollout to the change rather than duplicating flows or accepting a single conservative default. A correction to a form everyone has already filled in can reach everyone; a routine wording tweak can stay with new workers only.


What to expect

More flexibility means choosing the rollout path deliberately, based on the kind of change you are making. Apply to all Workers is the highest-impact option: it reopens the flow for workers who had finished, and if the change removes a task, that task and the responses already given to it are removed as well. Task status cannot be recovered afterward. On a flow with many workers, the update processes in the background and can take a few minutes to appear.


Availability

Coming soon to an initial group of customers — contact your Customer Success representative to learn more.

Powered by LaunchNotes