> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/superagents/schedules.md).

# Schedules

Have a superagent do work at set times, from a weekly briefing to a regular check on a model.

A schedule tells a superagent to do something at a set time, once or on a recurring basis. Schedules are how a superagent keeps ongoing work going, such as a weekly briefing or a daily check, without being asked.

## What a schedule does

Each schedule does one of two things:

| Type                | What happens                                                                            | Example                                                             |
| ------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Superagent turn** | The superagent wakes up and takes a turn of work, following the schedule's instructions | Every Monday, review last week's performance and update the backlog |
| **Team member run** | A specific worker or coordinator runs                                                   | Every weekday at 7:00, refresh the risk dashboard                   |

## Schedule settings

| Setting          | Details                                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------------------------- |
| **Title**        | A short name, such as "Weekly market briefing"                                                                 |
| **Directive**    | The instructions sent when the schedule fires                                                                  |
| **Frequency**    | A standard option, a custom cron expression, or **Once** for a single run. The shortest interval is 5 minutes. |
| **Time zone**    | The time zone the schedule runs in. It defaults to your browser's.                                             |
| **Backlog item** | Optionally, the backlog item the schedule's work belongs to                                                    |

After a schedule is created, you can change its title and directive. To change anything else, create a new schedule.

## Creating schedules

Schedules are created in three ways:

* **In the plan.** When you [create a superagent](/zerve-docs/superagents/create-a-superagent.md), the planner can propose schedules. They stay paused until you approve the plan, and you can remove any you don't want. Proposed schedules default to Sundays at 18:00 unless the plan says otherwise.
* **By the superagent.** As it works, a superagent can set its own schedules, for example to check back on a long-running job.
* **By asking.** Ask in a conversation, for example "Every weekday at 7am, check overnight moves in our largest positions."

Each schedule shows whether it was created by you or by the superagent.

## Managing schedules

The **Schedules** card on the superagent's Overview lists its schedules and when they'll next run. From there, you can:

| Action     | Effect                                            |
| ---------- | ------------------------------------------------- |
| **Pause**  | Stop the schedule from firing until you resume it |
| **Cancel** | Stop the schedule permanently                     |
| **Edit**   | Change its title or directive                     |

A schedule can also show as **completed**, when a one-off schedule has run, or **failed**.

## Getting the results

Scheduled work runs in the background. You'll find its results on the superagent's page, in its Activity, Outputs and backlog. If you've asked to be told about a piece of work, you'll get a follow-up message in that conversation when it's done. See [Follow-ups](/zerve-docs/superagents/conversations-backlog-and-follow-ups.md#follow-ups).

{% hint style="info" %}
Scheduled work doesn't currently post messages to [channels](/zerve-docs/superagents/channels.md) such as Slack or Telegram. Check the superagent's page or your conversations in Zerve for the results.
{% endhint %}

## When schedules don't run

Schedules don't fire while the superagent is **paused**. If its [daily budget](/zerve-docs/superagents/budgets-and-credits.md) is spent, the superagent can still respond in a limited way, but it can't start new work that uses credits until the budget resets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/superagents/schedules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.