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

# Scheduled tasks

> Have an AI coworker run the same task on a repeating schedule, like a daily briefing or a weekly report

A scheduled task is a saved instruction that an AI coworker runs on a repeating schedule. Use one for work that should happen without anyone asking: a morning briefing, a weekly report, a monthly check of your data.

## Create a scheduled task

You create scheduled tasks by asking the coworker. There's no form. Ask in Slack (in a DM or by @mentioning it) or in the coworker's **Chats** in Vybe.

**1. Describe the task**

Say what the coworker should do, when, and where the result should go. For example:

> Every Monday at 9am New York time, post a summary of last week's closed deals in #sales.

**2. Review the preview**

For a new report, the coworker first builds a preview from your real data and shows it to you. Ask for changes until it looks right.

**3. Confirm**

Tell the coworker to schedule it. It confirms with **Created scheduled task**, and the task appears under **Automations → Scheduled tasks**.

More examples:

> Every weekday at 8:30am, DM me my meetings for the day and any emails from customers that still need a reply.

> Every Friday at 3pm, check Linear for issues that have been in review for more than a week and list them in #engineering.

> On the first of each month, email [finance@acme.com](mailto:finance@acme.com) a summary of last month's Stripe payouts.

To change a task later, ask the same way:

> Move the weekly pipeline report to Mondays at 8am and include deals over \$10k only.

> [!TIP]
>
> Every run uses credits. Pick the least frequent schedule that's still useful. Hourly is rarely needed when daily will do.

### Where results go

A scheduled task does whatever its instructions say, so be explicit about the destination: a Slack channel, your DMs, or an email address. To post in a Slack channel, the coworker needs **Read and write** access to that channel. See [Slack](https://docs.vybe.build/channels/slack.md).

## Limits

| Limit | Value |
| - | - |
| Scheduled tasks per coworker | 50 |
| Shortest interval between runs | 5 minutes |
| Task name | Up to 100 characters, unique for each coworker |
| Task instructions | Up to 3,000 characters |
| Timezone | Any standard timezone, such as `America/New_York`. Tasks without one run in UTC. |

The coworker schedules tasks in your timezone unless you name a different one.

## Manage scheduled tasks

Open the coworker and go to **Automations → Scheduled tasks**. Each task shows:

* Its name and its schedule in plain words, with the timezone in parentheses. For example, "At 09:00 AM, Monday through Friday (New York)".
* An on/off switch. A task that's off doesn't run.
* **Run now**, which starts a run immediately. It's unavailable while the task is off.
* **Edit in Slack**, shown when the coworker is in Slack. It copies an edit request to your clipboard and opens Slack. Paste it into your conversation with the coworker and describe the change.
* The task's instructions, under the name.
* Chips for the actions each run is expected to take, such as sending a Slack message. If a run finishes without doing them, it shows a **Verification warning**.
* **Recent runs**, which expands to show past runs and their status. Use **Load more** for older runs.

The **Task options** (…) menu has **Run now** and **Delete**. Deleting asks for confirmation and can't be undone.

To see every scheduled run in one list, click **View activity**. It opens **Usage & Activity → Activity** filtered to scheduled runs.

## Delayed runs

Below the scheduled tasks, the **Delayed runs** list shows one-off runs the coworker scheduled for itself: "One-off checks the agent scheduled for itself. Each runs once, then it is done."

The coworker creates these when it starts something that finishes on its own and needs to come back to it. You'll see **Scheduled a check** in the conversation. You can also ask for one:

> Start the CRM export and let me know when the file is ready.

For each pending run you see when it will come back, for example "Coming back in 3 hours", with two actions:

* **Run now** starts it immediately.
* **Cancel** removes it.

Turn on **Show past** to see recent finished, cancelled, and skipped runs.

| Limit | Value |
| - | - |
| Delay for a check | 1 minute to 7 days |
| Delay for a follow-up | Up to 12 weeks |
| Pending delayed runs per coworker | 250 |

For anything that repeats, or that's further away than 7 days, use a scheduled task instead.

## Duplicated and ready-made coworkers

When you duplicate a coworker, or create one from a ready-made coworker in the [gallery](https://www.vybe.build/gallery), its scheduled tasks are copied but switched off. Review each task, then turn on the ones you want. Triggers aren't copied.

## When a task doesn't run

Check these in order:

1. **The task is off.** Turn its switch on.
2. **The coworker is archived.** Archiving stops all its scheduled tasks. Restore the coworker to start them again.
3. **The run was skipped.** Open **Recent runs** or **Activity**. A skipped run shows its reason: no credits left, or the coworker reached its monthly usage limit. See [Automations overview](https://docs.vybe.build/automations/overview.md#credits-and-limits).
4. **The run happened but the result went somewhere else.** Open the run in **Activity** to see what the coworker did, then ask it to update the task's instructions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.