Automations: Version History & Restore

Track, compare, and roll back automation edits with ease. The redesigned Version History gives you a clean sidebar, one-click restores, and smart version labeling—so you can build automations with total confidence, all at no extra cost.

What is Automation Version History?

Version History is Enrollio's built-in timeline of every saved state of your automation. Each entry records who edited it, the exact timestamp, and whether the version was a draft or published build.

You can browse, filter, and restore past versions of an automation in seconds—eliminating guesswork and risky re-builds. When you restore any version as a new draft, your live automation doesn't change until you publish. This follows the same draft → publish model used across Enrollio.

Key Benefits of Automation Version History

  • Instant peace of mind — Jump back to any of the last 10 versions (or 30 days) in one click
  • Team accountability — See every editor's name and the moment they saved
  • Flexible recovery — Convert a past version into a fresh draft or an entirely new automation
  • Zero learning curve — Clean sidebar UI with chronological labels (v12, v13, v14…)
  • Part of the Editing Trifecta — Works alongside Auto-Save and Undo/Redo at no extra cost

What's Included

Version History Revamp

Every saved version now captures your automation at a specific point in time—including editor, timestamp, and automation status (Draft or Published). Easily browse up to 10 versions or 30 days of version history, organized and filterable by editor.

Restore Previous Versions

Click Restore beside any version to reopen it as a new draft. You can even create a new automation from a previous version.

Enhanced Browsing Experience

The new Version History Sidebar gives you a clean, chronological overview with quick filters and clear version labels (v12, v13, v14…). Find exactly what you need—no guesswork, no clutter.

How Version History Is Created

Version History automatically records versions at key moments:

  • When you click Save manually
  • When you confirm changes in the Unsaved Changes pop-up
  • When you use Save Version in the automation builder
  • When the automation status changes (e.g., Draft → Publish or Publish → Draft)
Pro tip: Routine auto-saves don't create new versions by themselves. To capture your current state as a version, click Save Version—this snapshots your latest auto-saved changes into Version History.

Browse Versions

Open Version History to see your saved entries, organized by time and editor. Each entry shows:

  • Automation name
  • Version number (e.g., v12, v13, v14)
  • Timestamp
  • Editor
  • Status (Draft or Published)

You can filter by editor and view up to 10 versions or 30 days of history (whichever comes first).

Restore or Create from a Version

Click Restore next to any previous version to reopen it as a new draft. Your published automation remains unchanged until you publish the restored draft.

Or choose Create new automation from version to branch into a separate automation without touching the original.

When restoring:

  • The automation must be in Draft mode
  • There must be no enrolled families currently in the automation
  • The restored state becomes a new version—all prior versions remain available

How to Use Version History

  1. Open an automation and click the Version History icon in the sidebar
  2. Browse saved versions by timestamp and editor
  3. Click Save Version to snapshot your current auto-saved state
  4. Select any version → Preview (and Compare, if supported)
  5. Click Restore to create a new draft, or Create new automation from version for branching
  6. Test your draft and Publish when you're ready

Best Practices

  • Name versions at milestones (e.g., "Added tour confirmation sequence," "Updated waitlist follow-up")
  • Coordinate with your team—use Save Version before making large changes
  • Use Preview / Compare to validate differences before restoring
  • Branch safely with Create new automation from version when you want to explore big ideas without touching the current build
Pro tip: If you manage multiple centers, save a version before customizing an automation for a specific location. This makes it easy to roll back or compare location-specific changes.

Notes & Limitations

  • Draft → Publish: Restoring creates a new draft. You must publish to push it live
  • Undo/Redo resets after restore: Once you restore a version, your session history starts fresh from that draft
  • Auto Save scope: Auto Save covers canvas edits; some configuration panel edits may still require their own save/apply
  • Retention: Version History keeps up to 10 versions or 30 days
  • Validation to restore: Automation must be in Draft mode with no enrolled families
  • Availability: At launch, Version History is available via Labs Beta. Enable it in Settings → Labs for your account