Change the run status
PUT/dataset-run/:datasetRunId/update-status
Sets the run status. The automation uses Running at the start, Passed at the end and Failed when
something goes wrong.
FailedandStoppedclose the open step with the same status.Passed,Failed,StoppedandCancelledare final: they trigger the batch end notice and, withFailed, the rerun on error, when configured.Stoppeddoes not accept another status afterwards (409). To actually stop a run, usePUT /dataset-run/{id}/stop.
Send the status name (status) or its id (idStatus); with both, the name wins. Use only the run
statuses listed in status.
Along with Failed, the reason (reason) says why the run failed, without changing the status. Without a
reason, the failure counts as technical. The final status also records the end, the duration and the end
reason of the run (finishedAt, durationMs and endReason in GET /dataset-run/{id}). Sending the same
final status again changes nothing: when the automation sends Failed with the business reason and the
runner, at the end of the process, sends Failed again without a reason, the automation's end and reason
are kept.
Permission: Runs: update.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
Status changed. The response has no body.
Unknown status or one that is not a run status
Missing, invalid or expired token
The profile of the token user does not have the permission for the route
Run that does not belong to the organization
The run was already stopped (Stopped) and the requested status is a different one