deploy.jobs.runRun a job now, outside its schedule
Returns the run with status "requested"; the machine starts it within seconds. Read it back with runs.
Request syntax
POST /deploy/api/apps/{id}/jobs/{jobId}/runsPath parameters
idRequiredstring
Constraints: uuid
jobIdRequiredstring
Constraints: uuid
Response
202 with `data`: the run — id, status requested, trigger, instanceId (the machine that will run it), createdAt; the result fields stay null until it finishes. 409 when no machine of the app has reported in yet.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
Run idstatusAlwaysone of requested, running, succeeded, failed, timed_out, skipped, lost
requested, running, succeeded, failed, timed_out, skipped or losttriggerAlwaysone of schedule, manual
schedule or manual (run now)instanceIdAlwaysstring, may be null
The machine that runs it (i-…); null if it was deletedscheduledForAlwaysstring, may be null
The minute the schedule said; null for a run nowstartedAtAlwaysstring, may be null
When it started; null until thenfinishedAtAlwaysstring, may be null
When it finished; null until thenexitCodeAlwaysnumber, may be null
Exit code; null until it finishedoutputAlwaysstring, may be null
The last lines it printed (stdout and stderr)errorAlwaysstring, may be null
Why it ended without an exit code of its own; null otherwisecreatedAtAlwaysstring
When the run was recorded
Checked against the handlers: every route test validates their answers against this schema.
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 deploy:RunJob 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 deploy jobs run id jobIdcurl -X POST "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/jobs/jobId/runs" \
-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_deploy_jobs_run.