ci.runs.rerunStart a new run of the same workflow at the same commit
Planned from the workflow source the original run used, not the current file, so it reproduces what ran. Answers the new run.
Request syntax
POST /ci/api/runs/{runId}/rerunPath parameters
runIdRequiredstring
Constraints: uuid
Response
200 (not 201) with the new run, queued: same trigger, ref, commit, event and triggering user as the original, rerunOfRunId set to it. Any run may be re-run, one still in progress included. 400 when its stored workflow no longer plans; 404 when it is not in this organization.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ci:RerunWorkflow on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ci runs rerun runIdcurl -X POST "https://console.platform.deutschecloud.app/ci/api/runs/runId/rerun" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ci_runs_rerun.