Edit a live automation safely: draft, publish, versions Edits to a live automation are saved in a draft, and runs stay on the current version until you review the changes and publish. Every publish is a new version you can restore.
Before you start · for owners and managers
The permission to edit workflows
You need: The permission to edit workflowsSteps 1 Edit the live automation. It shows how many unpublished changes you have.
2 Press Publish .
What changes compares every change with the current version, and
Who this reaches shows the runs waiting mid-way.
3 Choose what happens to the waiting runs.
Keep them on the old version , or
Move them to the new one for the ones that can move.
4 Press Publish changes . To undo instead, open Versions and press Discard changes .
5 To restore an old version, open Versions and press Restore .
Where is your edit saved? The automation
The edit goes to
Never turned on, or turned off with no draft
The current version, directly
Live
The draft
Has a draft
The draft, until you publish or delete it
The name and description always apply straight away.
A draft that ends up matching the current version is deleted on its own.
Moving waiting runs Waiting at
Moves if the draft still has
A delay
A delay with the same steps after it. The set time doesn’t change
An approval
An approval with the same approve and reject paths
An action retry
The same type of action, with the same steps after it
A wait for a reply
The same answers going to the same steps
Anything else stays on its version and finishes there.
Versions Every publish that changes what the automation does makes a version. Changing the name or the position of the nodes doesn’t make a version.
Every run finishes on the version it started on.
Restoring goes to the draft if the automation is live.
The assistant writes to the draft and never publishes.
Editing at the same time If a teammate saved before you, you see “Someone else changed this workflow” or “The draft changed”. Press Reload , then make your edit again.
If something goes wrong What you see
Why
What to do
“Someone else changed this workflow”
Another version was published.
Press Reload .
“The draft changed”
A teammate edited the draft.
Reload.
“There’s no draft”
It was published or deleted.
Refresh the page.
“Too many waiting runs to move”
More than 20,000.
Publish and keep the runs where they are.
“The version doesn’t exist”
It was deleted under the retention rules.
Choose a newer version.
A real example The situation
Changing the reminder text while 40 runs are waiting.
What they did
They edited the text in the draft. The review: 40 runs at the delay, all movable. They published and moved them. The result
The waiting reminders went out with the new text, without breaking any run.
A made-up company, to show the idea. The numbers are rounded.
Good to know The last 20 versions are kept, plus any version a run is still running on. Up to 20,000 waiting runs can be moved in one publish. Did this guide solve it?
If not, we’ll ask what was missing.
We read every answer. To get a reply, use Contact support .
