Publishing and versions: draft vs published workflows

The canvas autosaves as you work, and what it saves is the draft. Run in the editor and Test this node always use the draft, so you can try a change the moment you make it.

Press Publish in the editor toolbar. Worfilo validates the draft the same way a run does; anything that would stop it running blocks the publish, while warnings, such as a tool list that may be out of date, are shown but do not.

A successful publish freezes the draft into a numbered version ("Published version 3") and makes it the active version straight away. A version never changes after it is made: later edits only ever change the draft, until you publish again.

• Editor Run and Test this node: the draft.
• Playground: the published version by default, or the draft if you switch it. A workflow that has never been published can only use the draft.
• Triggers: always the published version. See Schedules and triggers.
• Workflow API: always the published version. Calling a workflow that has never been published returns 409. See Workflow API.

Earlier versions are kept. To go back, the simplest way is to undo the change on the canvas and publish again, which makes a new version with the old behaviour.

A coding agent connected through the Worfilo MCP server can also activate an earlier version directly with its activate_version tool, which makes that version the one triggers and the API run.

Each run stores a snapshot of the graph it executed. Replaying an old run shows that graph, not today's draft or version, so you can always tell what a past run actually did. See Runs and replay.