Understanding flow versions and their management

Shrawani Bhattarai
Shrawani Bhattarai
  • Updated

Navigate Flows details page

Each modification to an activeInsert Definition Here flowInsert Definition Here results in the creation of a new flow version. This versioning system is vital for maintaining the integrity of workflows while allowing for ongoing improvements and adaptations. This article explores the nuances of flow versions, it’s history, and the management options available for each.

The concept of flow versions

Whenever an active flow is edited, a new version is created. This ensures that the original configuration remains intact and available for reference if needed. The Flow versionInsert Definition Here pane within the Flow detailsInsert Definition Here page acts as a logbook, chronicling version’s state, date and time. Each version is clickable, revealing its configuration in the Flow overviewInsert Definition Here pane, allowing Pendula users to understand and compare different iterations of the flow.

Activating new versions

When a flow is activated, the new flow goes live immediately. Activating a new version of a flow sets previous versions to a DrainingInsert Definition Here status. This ensures a seamless transition, allowing active experiencesInsert Definition Here to be completed without disruption.

For a detailed guide on the process, see Editing activated flows

Version management options

Click on any version listed in the Flow version pane to view or manage that particular iteration. Depending on the state of the selected version, the Edit and More options will change to reflect the flow state change command that can be used.

For example, an active version allows for edits, while a draining version does not offer the edit option but may allow duplication or termination. These actions are designed to manage the flow according to its current stage in the lifecycle.

For a detailed guide on flow states, see Manage individual flows in various states

The draining process

Draining is a critical process that occurs when a new flow version is activated. It prevents new experiences from starting in the older version while allowing ongoing experiences to reach their natural termination. The goal is to avoid any abrupt interruptions to the user's journey. During the draining phase, users also have the ability to terminate the version. Termination stops all activity within that flow version immediately.