Sign inGet started

Publish and manage automations

Publishing makes a saved workflow version available to new runs. Manage its lifecycle from Automations and the automation's detail page.
This guide covers the Automations dashboard preview, which is not yet generally available.

Before you publish

Review recipients, senders, message content, trigger settings, and failure paths. Complete a workflow preview and resolve blocking checks.

Save and publish

  1. Finish open field edits and select Save draft. Confirm the editor shows Draft saved.
  2. Select Publish to review the saved draft.
  3. Add an optional Version note describing the change.
  4. Select Publish version.
  5. Check the confirmation: an active version handles new runs; a published version on a paused automation remains paused until you resume it.
If publication reports an event-contract change, review how the event name or required data affects the connected application. Confirm the change after coordinating it with the application owner.
New runs use the active published version. Existing runs continue with the version they started with. Saving later draft changes does not update either group.
Publishing the workflow does not freeze a referenced SMS template. The SMS step uses its current published content at send time.
If another editor changed the draft, resolve the conflict before saving or publishing. Review the newer draft rather than overwriting it with an older view.

Review an earlier version

  1. Open the automation's Versions tab.
  2. Open the version to inspect its workflow and publication details.
  3. Select Restore to draft and review the comparison.
  4. Confirm the restoration, then check and preview the restored draft.
  5. Publish it when you want new runs to use that workflow.
Restoring to draft replaces draft content after review. It does not activate that content or change the original published version.

Pause and resume

Use Manage > Pause to stop new runs. Existing runs and their waits continue. Cancel an individual run separately when its remaining work should stop.
Use Resume when the published automation is ready to accept starts again. An unpublished draft must be published first. Scheduled workflows begin scheduling after resumption; they do not replay time spent paused.

Duplicate, archive, or restore

ActionResult
DuplicateCreates a named, independent copy of the saved draft. The copy is paused and unpublished, with no copied runs or version history. Save editor changes first if you want them included.
ArchivePauses new starts and moves the automation out of the Current list. Existing runs continue.
Restore from archiveReturns it to the Current list, still paused. Resume it separately when ready.
Use the Archived view on the Automations list to find archived workflows. Their retained versions and run history remain associated with the original automation.

Delete permanently

Select Delete permanently to remove the automation and its run history. New starts stop, and cancellation is requested for active runs. Cleanup continues after the request is accepted.
Deletion cannot be undone through the dashboard. A dispatched action can still finish, and aggregate statistics can remain after the automation is removed. Use archive when you need reversible retirement.

Next steps