Skip to main content

Restore an archived orchestration graph

POST 
/api/v1/orchestrations/:orchestration_id/versions/:version/restore

Writes an archived version's graph back as the orchestration's live definition, which archives it again as a new version rather than rewinding the counter — so a run pinned to any version in between still resolves the graph it started on.

The restore runs through the ordinary update path, so the archived graph goes through the same static validation as an authored one. Node resource references (agent_id, tool_id, orchestration_id) resolve when a run reaches the node, so a target deleted since the snapshot was taken restores cleanly and surfaces as a failed run rather than a 400. Restoring the graph the orchestration already holds is a no-op and archives nothing. Runs already in flight are unaffected either way — a restore is an ordinary edit, and pinning is what keeps it from reaching them.

Request​

Responses​

The orchestration, at its new version