Skip to main content

Resume Change Owner Process

Resumes a paused node ownership change process. The process returns to in_progress and continues from current_step_order; a step that already completed is not sent again, the next pending one is. See the overview for the lifecycle.

If the process was paused because a step failed, use Retry Change Owner Process Step instead. Resume does not re-run a failed step: the process reads in_progress but stays on that step. To recover from that, pause the process and retry the step.

Only the platform owner's API key may call this endpoint; any other key gets 403.

Required permission: node:change-owner

Request​

POST /v2/admin/nodes/{node_id}/change-owner-processes/{process_id}/resume

Parameters​

NameTypeInDescription
node_idstringpathRequired. The node that owns the setup
process_idstringpathRequired. The process id; must belong to node_id

Headers​

NameDescription
AuthorizationRequired. Bearer <access_token>

Example​

curl --request POST \
--url '{{baseUrl}}/v2/admin/nodes/6901350deb7ed8c1c38de4e9/change-owner-processes/6907a4e1b5c83f2d9e6a0b17/resume' \
--header 'Authorization: Bearer <access_token>'

Response​

204 No Content, no body. The process status is now in_progress. If the continuation cannot be queued, the process is put back to paused and the call fails; it is safe to call again.

Errors​

StatusCodeDescription
40010000process_id is not a valid id
40020001No process with this id on this node
40020003The process is not paused
40310005The API key does not belong to the platform owner
50010000The continuation could not be queued; the process stays paused

See Errors for the error format and common codes.