> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blobhub.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Schedule

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

| Parameter     | Type   | Required | Description                            |
| :------------ | :----- | :------- | :------------------------------------- |
| `engine`      | string | Yes      | Must be `scheduler_blobhub`.           |
| `command`     | string | Yes      | Must be `delete_schedule`.             |
| `schedule_id` | string | Yes      | Id or alias of the schedule to delete. |

### Response

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

### Errors

| Status | Error       | Cause                                                                   |
| :----- | :---------- | :---------------------------------------------------------------------- |
| 403    | `forbidden` | The schedule does not exist, or it is not reachable from this revision. |

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](/blob-types/workflow/operations/close-session).

### Example

<CodeGroup>
  ```json Request theme={null}
  {
    "engine": "scheduler_blobhub",
    "command": "delete_schedule",
    "schedule_id": "sched-001"
  }
  ```

  ```json Response theme={null}
  {
    "status": "success"
  }
  ```
</CodeGroup>