# Resume an orchestration run

> Re-drives an awaiting_input orchestration run from its last checkpoint. This does not satisfy the pause itself — it carries no node_id or payload, so a run parked on a human or webhook-receive node re-parks on the same node. Use submit-human-input to supply the awaited payload and advance the run.

<Heading
  as={"h1"}
  className={"openapi__heading"}
  children={"Resume an orchestration run"}
>
</Heading>

<MethodEndpoint
  method={"post"}
  path={"/api/v1/orchestration-runs/{orchestration_run_id}/resume"}
  context={"endpoint"}
>
  
</MethodEndpoint>

Re-drives an awaiting_input orchestration run from its last checkpoint. This does not satisfy the pause itself — it carries no node_id or payload, so a run parked on a human or webhook-receive node re-parks on the same node. Use submit-human-input to supply the awaited payload and advance the run.
It is also the only thing that lifts an operator pause (pause-orchestration-run): a run parked with `required_action.type` of `paused` re-drives the frontier that had not run yet, and one paused mid-timer goes back to `sleeping` for the wake it was already due.

<Heading
  id={"request"}
  as={"h2"}
  className={"openapi-tabs__heading"}
>
  <Translate id="theme.openapi.request.title">Request</Translate>
</Heading>

<ParamsDetails
  {...require("./resume-orchestration-run.ParamsDetails.json")}
>
  
</ParamsDetails>

<RequestSchema
  {...require("./resume-orchestration-run.RequestSchema.json")}
>
  
</RequestSchema>

<StatusCodes
  {...require("./resume-orchestration-run.StatusCodes.json")}
>
  
</StatusCodes>