---
title: "Pause, resume or delete a scheduled brief or a monitor"
method: POST
path: "/api/v1/tools/manage_scheduled_task/execute"
tags: ["Adako"]
---

# Pause, resume or delete a scheduled brief or a monitor

`POST /api/v1/tools/manage_scheduled_task/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/manage_scheduled_task/execute`
- Auth: HTTP bearer

Pauses, resumes or deletes one recurring brief or one monitor. Adako settings only; nothing on the ad platform changes, past reports stay readable and proposals a monitor already made stay in the approvals inbox.
Use when: the user says a brief is too frequent, an alert is too noisy, or wants either one back.
Name what you are acting on: task_id for a brief, monitor_id for a monitor. Both come from list_scheduled_tasks; monitor ids also come from list_monitors. Pass one, never both.
Prefer pause over delete: a paused brief keeps its settings, a paused monitor keeps its history, and either resumes in one call. Deleting needs confirm_delete: true — a schedule cannot be recovered and a deleted monitor takes its evaluation history with it.
Do not use when: the user wants a monitor's threshold or rule changed — that is update_monitor.
Returns the new state of whichever one you named.
If you are unsure whether the user means a brief or a monitor, call list_scheduled_tasks and ask.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `task_id` string: Id of a scheduled brief, from list_scheduled_tasks. Pass this or monitor_id.
    - `monitor_id` string: Id of a monitor, from list_scheduled_tasks or list_monitors. Pass this or task_id.
    - `action` 'pause' | 'resume' | 'delete', required: pause stops delivery or evaluation and keeps the settings; delete removes the schedule or the monitor.
    - `confirm_delete` boolean: Must be true to remove anything. Ask the user first.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)