Skip to main content
Delete a schedule and all of its associated execution records. The schedule is also removed from the underlying scheduling service and will no longer fire.

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

Request Body

Response

Returns {"status": "success"} — no body beyond the status.

Errors

A caller cannot tell these 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