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

# Cancel schedule

> Cancels the conversation's active schedule (a message or an AI execution)

<Info>
  **Endpoint** · `POST /conversation/actions`
</Info>

Cancels the conversation's active schedule (each conversation has at most one):
either a human's scheduled message or a scheduled AI execution. No fields.
Idempotent: if there's no active schedule, it succeeds with `cancelled: false`.

```jsonc theme={null}
{
  "type": "cancel_schedule"
}
```

In a list, this object goes in the `actions` array of a `POST /conversation/actions` — see [Assembling an action list](/en/action-groups/overview#assembling-an-action-list).

## Executable example

A `cancel_schedule` on a conversation identified by phone and channel. It cancels
the conversation's active schedule (a message or an AI execution); it takes no
fields and is idempotent.

### Request

```bash theme={null}
curl -X POST "https://app.1to1.ai/api/v1/public/{slug}/conversation/actions" \
  -H "Authorization: Bearer sk_1to1_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "conversation": {
      "phone": "+5215512345678",
      "channel": "ch_7A9K2M4Q"
    },
    "actions": [
      {
        "type": "cancel_schedule"
      }
    ]
  }'
```

### Response

`202 Accepted` — the group was accepted and runs in the **background**. The
per-action result does not travel in the response (query it later — see [How it runs](/en/action-groups/overview#how-it-runs)).

```json theme={null}
{
  "status": "processing",
  "actions_accepted": 1
}
```

<ResponseField name="status" type="string">
  Always `processing`: confirms the group was accepted and is running.
</ResponseField>

<ResponseField name="actions_accepted" type="integer">
  How many actions in the array were **admitted** for execution — not how many
  succeeded.
</ResponseField>