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

# Cron

> Give your agent a schedule of its own — created in chat, mirrored read-only on the agent page.

The cron channel lets an agent run itself on a schedule — a recurring check, a periodic report, a one-off reminder — without waiting for a person or an external system to trigger it.

<Note>
  Scheduled tasks are created **by the agent**, not through a form. There is no "new task" button — you ask the agent to schedule something in chat, the same way you'd ask a colleague.
</Note>

## Creating a scheduled task

Just tell the agent what you want and when, in plain language:

* "Every Monday at 9am, pull last week's numbers and post a summary here."
* "Check our top competitor's pricing page every day at 7am and flag anything that changed."
* "In three hours, follow up with the customer if they haven't replied."
* "On the 1st of every month, close out last month's expenses and send me the total."

The agent interprets the request, sets up the schedule, and confirms it with you. From then on, it runs on its own.

## The Cron Jobs tab

The agent page's **Cron Jobs** tab shows every scheduled task the agent has created, with its next run, last run, and last state — but it's a **read-only mirror**, not a scheduler UI. You can see what's scheduled and review what happened on each run, but you can't create, edit, or delete a task directly from it.

## Anatomy of a run

Each run recorded in the tab shows:

| Field   | Details                                                                                  |
| ------- | ---------------------------------------------------------------------------------------- |
| Output  | Up to 8,192 characters of what the run produced                                          |
| Summary | A short, up-to-500-character summary of the run                                          |
| Status  | A **business outcome** — `ok` or `failed` — separate from the technical execution status |

The business status reflects whether the agent judged the run to have actually accomplished what it was asked to do, which can differ from whether the run technically completed without error.

## Notifications

Notifications follow a deliberately asymmetric rule, designed to keep you informed without spamming you for routine successes:

| Outcome                 | Notification | Message in your chat |
| ----------------------- | ------------ | -------------------- |
| Any failure             | Yes          | Yes                  |
| One-off task succeeds   | Yes          | Yes                  |
| Recurring task succeeds | Yes          | No                   |

A recurring task that keeps succeeding stays visible in the notification list and the Cron tab, but won't post a fresh message into your chat every single time it runs — only when something needs your attention, or the first (and only) time a one-off task completes.

## Modifying or deleting a task

There's no edit or delete control in the tab. To change a schedule, adjust what a task does, or cancel it, ask the agent directly in chat — for example, "cancel the weekly summary" or "move the daily check to 8am instead."

## See also

* [Channels overview](/channels/overview) — principles shared across all channels
* [Chat](/guides/chat) — where you create and manage scheduled tasks
* [Activity](/guides/activity) — every cron run appears in the timeline tagged with the cron badge