deploy.jobs.updateChange a job, or enable/disable it
schedule is a five-field cron expression in UTC (minute hour day-of-month month day-of-week, or @hourly/@daily/@weekly/@monthly/@yearly). The command runs with /bin/sh -c in the app’s image with its full environment, on one of the app’s machines, which keeps the schedule itself. Fields left out keep their value.
Request syntax
PATCH /deploy/api/apps/{id}/jobs/{jobId}
{
"name": "string",
"schedule": "string",
"command": "string",
"service": "string",
"enabled": "boolean",
"timeoutSec": "number",
"concurrency": "enum",
"timezone": "object"
}Path parameters
idRequiredstring
Constraints: uuid
jobIdRequiredstring
Constraints: uuid
Request body
nameOptionalstring
Name of the job, unique within the app
Constraints: 1-63 chars, /^[a-z0-9]([a-z0-9-]*[a-z0-9])?$/
scheduleOptionalstring
When it runs: a five-field cron expression in UTC, or @hourly, @daily, @weekly, @monthly, @yearly
Constraints: 1-200 chars
commandOptionalstring
Command run with /bin/sh -c in the app’s image, with the app’s environment
Constraints: 1-4096 chars
serviceOptionalstring
Compose apps only: the service whose image and environment the job runs with; omitted or null, the published service
Constraints: 1-63 chars
May be null.
enabledOptionalboolean
Whether the job runs on its schedule; a new job is enabled unless this is false
timeoutSecOptionalnumber
Seconds a run may take before it is stopped; a new job gets 3600
Constraints: integer, 10-86400
concurrencyOptionalenum
What happens when a run is due while the previous one is still going: skip (a new job’s default) records it as skipped, allow starts it anyway
One of:
skip,allowtimezoneOptionalobject
Time zone of the schedule; only UTC
Constraints: JSON
Response
200 with `data`: the job after the change, as list returns it.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
Job idnameAlwaysstring
Name, unique in the appscheduleAlwaysstring
Cron expression, in UTCscheduleDescriptionAlwaysstring
The schedule in words, or why it cannot be readcommandAlwaysstring
Command run with /bin/sh -cserviceAlwaysstring, may be null
Compose apps: the service it runs in; null: the published servicetimezoneAlwaysstring
Time zone of the schedule (UTC)enabledAlwaysboolean
Whether it runs on its scheduletimeoutSecAlwaysnumber
Seconds a run may take before it is stoppedconcurrencyAlwaysone of skip, allow
skip: a due run is skipped while the previous one runs; allow: it starts anywaynextRunAtAlwaysstring, may be null
When it runs next; null when disabledlastRunAlwaysobject, may be null
Its newest run; null if it never ranlastRun.idAlwaysstring
Run idlastRun.statusAlwaysone of requested, running, succeeded, failed, timed_out, skipped, lost
requested, running, succeeded, failed, timed_out, skipped or lostlastRun.triggerAlwaysone of schedule, manual
schedule or manual (run now)lastRun.exitCodeAlwaysnumber, may be null
Exit code; null until it finishedlastRun.startedAtAlwaysstring, may be null
When it startedlastRun.finishedAtAlwaysstring, may be null
When it finishedlastRun.createdAtAlwaysstring
When the run was recordedcreatedAtAlwaysstring
When it was createdupdatedAtAlwaysstring
When it was last changed
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:UpdateJob 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 update id jobIdcurl -X PATCH "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/jobs/jobId" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_deploy_jobs_update.