How-to

Restore a version

Integrations keep an append-only history. You never edit a published graph in place. Saving after publish clones a new draft, writes the graph, then publishes again.

Version states

At most one version holds the live compiled build. GET /workflows/{id}/versions returns status, timestamps, node/edge counts, has_compiled_build, and a short change summary versus the previous version.

Fork-forward (the usual restore)

Use this when you want yesterday’s graph as today’s starting point.

1. Open the integration → History.
2. Select a version. The graph is read-only.
3. Restore as new draft.
4. Edit if needed. Save (and publish, if you work from the API).

curl -s -X POST "$SIRIUS/workflows/$WF/versions/3/revert" \
  -H 'content-type: application/json' \
  -d '{"message":"restore after bad mapping","restore_connectors":true}'

This clones the graph (and optionally the connector snapshot) into latest+1 as a draft. It does not auto-publish. Audit: workflow:revert with mode=fork.

Reactivate (ops)

Use this when a published build was good and you need the runtime on it now. Drafts stay intact.

curl -s -X POST "$SIRIUS/workflows/$WF/versions/2/reactivate" \
  -H 'content-type: application/json' \
  -d '{"tenant_id":"default"}'

The target must already be published. Requires publish permission. The console asks for confirmation. Audit: mode=reactivate.

Save notes

On Save, add a short note. History shows it next to the change summary so the next person knows why the graph moved.

History is not a visual diff. You get counts and the graph itself. For a portable copy of the integration, use Export and import.