Skip to main content

Drafts, publishing and pausing

A workflow has its own name and enabled state, plus versioned executable content. It can have one editable draft and one current publication. Older publications remain history.

Save and preview a draftโ€‹

Save as you build, even if some fields or connections are incomplete. Validation issues explain what blocks publication. Saving does not update the live workflow.

Preview evaluates the current editor definition without creating effects. A preview can include unsaved edits, so save the final definition before publishing. Resolve publication issues such as missing outcome connections, invalid mappings or incomplete Script/Agent configuration.

Publishโ€‹

Publishing freezes the chosen version and its exact dependencies. The first publication enables the workflow. Subsequent publications preserve whether it is live or paused.

Future runs use the new current publication. Runs already admitted keep their earlier publication, dependencies and captured input, even if they are still waiting for a person. Changes to Script and Agent steps take effect when their workflow draft is published.

Make another changeโ€‹

Create an editable version, optionally copying an existing version of the same workflow. There can be only one working version at a time. Edit it, review the changes and publish when ready.

Discarding a draft does not remove the current publication. Published content cannot be edited or deleted in place. To return to earlier behavior, copy that version into a new draft, review it and publish the new version. This does not rewind existing runs.

Metadata changes such as renaming do not need publication. If another edit conflicts with yours, reload and review the latest state before saving again.

Pause or cancel?โ€‹

IntentionOperationExisting results
Stop new startsPause the workflow. Existing runs continue.Remain.
Stop one active runRequest cancellation from that run.Already committed effects remain.
Resume future startsEnable the published workflow.Past events and paused schedule occurrences are not replayed.

Workflow deletion has active-run restrictions; inspect open runs before deleting. Retained runs remain inspectable after parent deletion. Deletion does not undo their business effects.

See Monitoring runs and the version API reference.