Restoring a Previous Workflow Version (Why It Moves Forward, Not Back)
Restoring an older version of a workflow writes it forward as a brand-new version instead of rewinding — worth knowing before you click Restore.
Workflows keeps a full version history for every automation, and clicking Restore on an older version does something slightly different from what most people expect.
What actually happens
Every saved change to a workflow is recorded as a version. When you restore an earlier one from the history panel, the platform doesn't rewind the workflow back to that point in time — it takes the content of that older version and writes it forward as a brand-new version on top of everything that came after it.
Why that distinction matters
If you're used to version control tools where "revert" and "reset" mean different things, this is closer to a revert: nothing in between gets erased, and the version history keeps growing forward rather than being truncated. Practically, that means you can always get back to where you just were before the restore — it's just one more version in the list, not a deletion of the ones you're moving past.
What to expect in the UI
Open the version-history panel, pick the version you want, and restore it — the workflow updates to match that content immediately, and a new version number is created to represent the restored state. Nothing about the versions you're skipping past disappears.
We're calling this out directly because a "restore" that behaves like a forward commit rather than a rewind is easy to misjudge the first time — better to know the mechanic going in than to be surprised by what the version list looks like afterward.