Skip to main content

Publish, drafts, and versions

How editing, publishing, and versions work.

Editing a workflow is safe: your changes stay in a draft until you publish, and runs already in progress aren't disrupted.

Drafts autosave

As you edit on the canvas, your changes autosave to a draft. Nothing in the draft runs — it's yours to shape until you're ready.

Publish to go live

Click Publish changes to make your draft the live version. If any step still needs setup, publishing is blocked and those steps are flagged red — the button tells you how many to finish. Once they're valid, publishing shows a "Published" confirmation.

"No one sees these results"

If your workflow ends in a step that doesn't get results in front of anyone — Generate CSV link or Summarize run, with nothing after it — publishing shows a warning: "No one sees these results." It names what the workflow ends in and suggests a step that would deliver it, usually Notify.

This doesn't block you — click Publish anyway if you're testing, or you're happy to collect the file yourself. It only checks the path results actually take: if at least one branch arm ends in a delivery step, the warning doesn't fire even if another arm doesn't deliver.

Discard changes

To throw away unpublished edits and return to the live version, click Discard changes and confirm. This can't be undone.

Versions and in-flight runs

Each publish creates a new version. A run always finishes on the version it started on, so publishing a change never disrupts records already moving through the workflow — they complete on their original steps, and new runs use the new version.

Best practice

  • Test with Trigger workflow and a small limit before turning a workflow Live.

  • Publish deliberately — a published change takes effect on the next run.

Did this answer your question?