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

# Schedules

> Run Minerva Agent at a set time, once or on a repeating cadence

A schedule runs Minerva Agent for you at a set time and saves the result to a chat or a report. Use it for work you want on a regular cadence, such as a weekly performance summary.

## Before you start

* **Connect your data.** Unlike a regular chat, a schedule needs your connected data to be ready for analysis, both when you save it and each time it runs.
* **Write instructions that stand alone.** Nobody is there to answer a follow-up question when a schedule runs.
* **Use relative periods.** Write "the previous week", not a fixed date that will be wrong next month.

## Create a schedule

**1. Open Schedules**

Go to [**Agent → Schedules**](https://app.minerva.io/agent/schedules) and select **New schedule**.

**2. Name it and write the instructions**

Enter a **Name**. Under **Instructions**, describe the task in full: the metrics, the period, any comparison and the output you expect.

**3. Set when it runs**

Choose **Once** or **Repeat**. A repeating schedule runs every 1 to 12 days, weeks or months. Pick the start date and the **Time of day**, and check the time zone shown next to it.

**4. Choose the output**

Under **Delivery**, set **Output** to **Chat** or **Report**. **Report** is selected by default.

**5. Choose where it lands**

Under **Deliver to**, choose **A new chat each run** or one of your own chats.

**6. Create and test it**

Select **Create schedule**. Use **Run now** to try it before the first scheduled run.

> [!NOTE]
>
> **Run now** uses the saved schedule. If you've changed something in the editor, select **Save changes** first.

## Create a schedule from a chat

Ask the Agent for a future or repeating task and say when it should run.

* For a repeating task, the Agent shows a proposal. The schedule starts once you create it from the proposal.
* For a one-time reminder, the Agent can create it right away, with an option to undo.

## Manage a schedule

| Action | What it does | What it doesn't do |
| - | - | - |
| **Pause** | Stops future runs. | Stop a run that has already started. |
| **Resume** | Turns future runs back on. | Run the ones that were missed while it was paused. |
| **Run now** | Starts one run of the saved schedule. | Resume a paused schedule. |
| **Delete schedule** | Removes the schedule, after you confirm. | Remove the chats and reports from past runs. |

## Where results go

| Output | Deliver to | Result |
| - | - | - |
| **Chat** | A new chat each run | A new chat for every run. Open it from the run with **Open chat**. |
| **Chat** | One of your own chats | The run is added to that chat. |
| **Report** | Either option | A saved report, with a chat that records the run. Open it from the run with **Open report**. |

Results are saved in Minerva, to the chat or report you chose.

## When a run doesn't finish

Each run appears under **History** with a status: **Completed**, **Failed**, **Running**, **Skipped**, **Stopped**, **Timed out** or **Unavailable**.

* **A failed run pauses a repeating schedule.** Check what went wrong, fix the instructions or the data, try **Run now**, then **Resume**.
* **A run is skipped if the previous one is still going.** It's also skipped if the chat it saves results to is busy.

The schedule shows its most recent 20 runs. Older results stay in your chats and reports.

## Limits and billing

* A name can be up to 100 characters. Instructions can be 10 to 8,000 characters.
* Schedules repeat in days, weeks or months. There is no hourly option.
* Scheduling doesn't use your record export allowance.
* A schedule doesn't activate segments on its own. An activation needs you to confirm it.


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