Workflow versions and restoration
Compare saved definitions and restore an earlier workflow without rewriting execution history.
Workflow versions preserve snapshots of a definition so you can understand changes and return to an earlier configuration. Use them for controlled changes to prompts, sources, triggers, or graph structure.
A version is a definition snapshot, not a copy of all external data. Restoring it changes the current workflow; it does not retract earlier writes or recreate deleted source files.
Compare versions
Review version history from newest to oldest, then compare the relevant snapshots. The comparison identifies changes to the name, trigger, and enabled state, along with added, removed, and modified jobs.
For a changed job, inspect its configuration and dependencies as well as its handler name. A small prompt or JSONPath change can alter output substantially even when the topology is unchanged.
Compare a historical version against the current definition when investigating a regression. Record the run's own published version where available, rather than assuming it used today's editor contents.
Restore carefully
- Identify the last known suitable version.
- Compare it with the current definition.
- Confirm that its connections, handlers, and extensions remain available.
- Restore the snapshot using the supported version operation.
- Validate the restored workflow and check its enabled state and trigger.
- Run a limited example and inspect the result.
Restoration preserves the pre-restore state as a new history entry, making the definition change reversible. Existing executions keep their historical identity.
Handle concurrent changes
A save, publication, or restore can conflict with another person's newer edit. A revision conflict means the operation did not apply to the version you reviewed. Refresh, compare, and decide how to merge your intended changes. Do not overwrite the new head simply to clear the error.
Distinguish restoration from rollback
A workflow restore edits its current definition. An app rollback selects an earlier app release and its pinned workflow context. Neither operation guarantees reversal of external business actions.
For shared recipe changes, preview an upgrade rather than editing an immutable library definition. See reusable recipes, publishing workflows, and reliability.