Skip to main content
Update attributes of an existing schedule. Only fields supplied in the request are changed; omitted fields keep their current values. A schedule in the completed state cannot be updated.

POST /revisions/:id/data/command (Command: update_schedule)

Request Body

An absent description means “leave unchanged”; a description present with an empty value does not. "description": "" is a write that clears it — get_schedule and list_schedules then return no description key.
If repeat is changed to recurring_cron, cron_expression must be supplied in the same request. If changed to one_time, invocation_time must be supplied. invocation_time follows the same naive-datetime format as on create.
See Alias Grammar for the character rules, length limits, and the id-shape restriction — an alias may not be shaped like a UUID.

Response

Errors

A caller cannot tell the schedule’s two 403 cases apart — a schedule that does not exist and one that is not reachable both answer forbidden. Sessions already work this way; see Close Session.

Example