> 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/ship-your-work/scheduled-jobs.md).

# Scheduled jobs

Run a project automatically on a schedule.

A **scheduled job** runs a project automatically, such as every morning before markets open, or at month end.

## Setting a schedule

| Setting                   | Options                                                                                           |
| ------------------------- | ------------------------------------------------------------------------------------------------- |
| **Frequency**             | **Daily**, **Weekly** or **Monthly**, at a time you choose, or **Custom**, with a cron expression |
| **Email alerts**          | Get an email about each run                                                                       |
| **Email on failure only** | Only get an email when a run fails                                                                |

The shortest interval between runs is 5 minutes.

## In the notebook view

Each notebook can have a scheduled job, which runs the notebook's blocks. Set it up from the notebook's scheduled job settings.

## In the canvas view

In the canvas view, scheduled jobs are [layers](/zerve-docs/notebooks/layers.md). Add a **Scheduled Jobs** layer, add the blocks it should run, then give the job a name and schedule, and turn it on.

While a layer's scheduled job is active, its blocks are read-only. Turn the job off to edit them.

## Checking runs

Every scheduled job keeps a history of its runs. If a block fails during a run, the run fails; use the run history to find and fix the error.

You're notified if a scheduled job is paused. See [Preferences and notifications](/zerve-docs/administration/preferences-and-notifications.md#notifications).

## Scheduled agent runs

When a schedule runs the agent, it uses **Build** mode, since there's nobody there to approve a plan. See [Agent modes](/zerve-docs/agents-in-the-workspace/agent-modes.md).

For a superagent's schedules, see [Schedules](/zerve-docs/superagents/schedules.md).


---

# 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/ship-your-work/scheduled-jobs.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.