Restore an archived orchestration graph
POST/v1/projects/:project_id/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
- 200
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
The orchestration, at its new version
Bad Request — version is not a positive integer
Unauthorized
Forbidden
Not found
The resource has moved past the version this write read (VERSION_CONFLICT): a stated expected_version or If-Match no longer matches, or a concurrent write took the version first. meta.current_version names the version in force. Nothing is written.
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there