Skip to main content

Version History and Restore Functionality in Workflows

Version History allows users to view, save, restore, and duplicate previous workflow versions so changes can be tested, reviewed, or reverted safely without affecting live automations.

Updated over 3 months ago

Who This Is For / When to Use

This article is for Kyrios users who edit workflows and need a safe way to track changes, recover previous logic, or create new workflows from earlier versions. Use Version History when testing updates, troubleshooting issues, or restoring prior workflow configurations.

What Version History Does

Version History records saved workflow versions and allows users to restore or duplicate them as drafts. It works alongside auto-save and undo/redo to provide a controlled and reversible workflow editing experience.

How Version History Is Stored

Version History is retained using the following rules:

  • Up to 10 saved versions, or

  • 30 days of history, whichever limit is reached first

Each version includes metadata such as version number, timestamp, editor, and workflow status.

What Information Each Version Shows

Each saved version displays:

  • Workflow name

  • Version number (for example, v12 or v16)

  • Date and time saved

  • Editor initials

  • Workflow status (Draft or Published)

This allows users to clearly identify when and why a change was made.

How to Open Version History

Version History is accessed directly from the workflow builder.

Steps

  1. Open Automation β†’ Workflows.

  2. Open the workflow you want to review.

  3. Click the Version History icon in the left sidebar.

  4. The Version History panel opens on the right.

Saving a Version Manually

Auto-saved changes do not create a version automatically. A version must be saved manually.

To save a version:

  1. Make changes in the workflow builder.

  2. Click Save Version in the Version History panel.

  3. A new numbered version is created from the current auto-saved state.

This snapshot can be restored or duplicated later.

Restoring a Previous Version

Restoring a version allows users to revert workflow logic safely.

When Restore is clicked:

  • The selected version opens as a new draft

  • The current live workflow remains unchanged

  • The restored draft can be edited and published when ready

Important
All enrolled contacts must complete or exit the workflow before restoring a version.

Creating a New Workflow from a Version

Instead of restoring over an existing workflow, users can duplicate a version.

Using Create new workflow from version:

  • Creates a separate workflow

  • Uses the selected version as the starting point

  • Allows testing or branching without impacting the original workflow

This is ideal for experimentation or A/B logic testing.

How Version History Protects Your Work

Version History works with:

  • Auto-Save (continuous background saving)

  • Undo and Redo (step-by-step editing recovery)

Together, these features ensure workflow changes are recoverable and safe.

Common Questions

Does restoring a version delete my current workflow?

No. Restoring creates a new draft. Your current published workflow remains live until you choose to publish the restored version.

Can I restore a version while contacts are enrolled?

No. All contacts must complete or exit the workflow before a version can be restored.

How many versions can I view?

You can view up to 10 versions or 30 days of history, whichever comes first.

Do auto-saved changes appear in Version History?

No. Auto-saved changes are not added to Version History unless Save Version is clicked.

What happens when I create a new workflow from a version?

A completely separate workflow is created using the selected version as its base.

Can restored versions be used for testing?

Yes. Restored drafts and duplicated workflows are ideal for testing new logic without affecting live automations.

Did this answer your question?