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

# Schedules

> Choose when a schedule launches, who it runs as, why Oqoqo pauses it, and how many runs its launches need.

A **schedule** relaunches a finished experiment on a recurring cadence—such as every weekday morning—so you can track pass rates and catch regressions over time. Each launch creates a new experiment using the latest saved versions of its tasks and treatments, identical to [Launch again](https://docs.oqoqo.ai/experiments/launch.md#launch-again).

## Create a schedule

You need at least one finished experiment.

> [tab] Dashboard
>
> 1. Select **Schedule** on a finished experiment (or open **Automate → Schedules**, select **New schedule**, and pick an experiment).
> 2. Set **Repeat**, time, and **Time zone**.
> 3. Review **First launch** and **Uses** (run forecast), then select **Create schedule**.

> [tab] CLI
>
> Preview the schedule first, then create it (use a quarter-hour minute `0`, `15`, `30`, or `45` and an IANA `--time-zone`):
>
> ```bash theme={null}
> oqoqo schedules preview exp_8f2c41d0 --cron "0 9 * * 1-5" --time-zone America/New_York
> oqoqo schedules create exp_8f2c41d0 --cron "0 9 * * 1-5" --time-zone America/New_York
> ```
>
> See [`oqoqo schedules create`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-create).

> [tab] Plugin (MCP)
>
> Ask your AI assistant to schedule the experiment. It calls **Preview a schedule** ([`preview_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#preview_schedule)) and **Create or change a schedule** ([`manage_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#manage_schedule)). Approve the creation call in your host.
>
> ```text theme={null}
> Schedule experiment exp_8f2c41d0 to launch every weekday at 9:00 AM New York time.
> ```

The schedule dialog previews the **First launch** timestamp and the **Uses** run estimate (runs per launch and over the next 30 days). If your run balance won't cover upcoming launches, you can still create the schedule and add runs before the shortfall date.

![Schedule dialog with Repeat, At, Time zone, First launch, and the runs that each launch uses.](https://mintcdn.com/oqoqo/YO1ysyUx4SPwBwoz/images/screenshots/schedule-dialog-light.png?fit=max\&auto=format\&n=YO1ysyUx4SPwBwoz\&q=85\&s=95eabb6b07957c8b550fc6a9a05f32ed)

> [!NOTE]
>
> Schedules fire on the quarter hour (`00`, `15`, `30`, or `45`), at most once per hour. Each project supports up to 50 active schedules.

## Choose when it launches

Pick **Every hour**, **Every day**, **Every weekday**, **Every week**, **Every month** (use **Last day** to run every month without skipping 30-day months or February), or **Custom** with a 5-field cron expression (such as `30 8 * * 1,3,5`).

The **Time zone** defaults to your browser's zone and follows daylight saving time automatically. In the CLI and plugin, pass an IANA time zone name like `America/New_York`, `Europe/London`, or `UTC` (abbreviations like `EST` are rejected).

> [accordion] Time zone normalization and schedule names
>
> * `GMT` and `Etc/GMT` normalize to `UTC`; legacy names such as `US/Pacific` and `Asia/Calcutta` normalize to `America/Los_Angeles` and `Asia/Kolkata`.
> * New schedules inherit the source experiment's name until you rename the schedule on its detail page.
> * Each experiment's **⋯** menu and info popover link directly to any schedule that launches or launched it.

## Manage a schedule

Open any schedule under **Automate → Schedules** to inspect its cadence, next run, run forecast, status (**Active**, **Paused**, or **Needs attention**), and **Experiments**, **Runs**, and **Frictions** tabs.

```mermaid theme={null}
flowchart LR
  A["Active"] -- "Pause" --> P["Paused"]
  P -- "Resume" --> A
  A -- "Blocker, 3 skips, or personal edit" --> N["Needs attention"]
  N -- "Fix & Resume" --> A
```

| Action | Effect |
| - | - |
| **Launch now** | Launches immediately under your own account without shifting the next scheduled run (disabled if the previous run is still active). |
| **Edit** | Updates the source experiment, cadence, or time zone after validating launch readiness. |
| **Pause** / **Resume** | Stops or restarts scheduled runs. Resuming validates launch readiness first and waits for the next scheduled slot. |
| **Delete** (in **⋯**) | Deletes the schedule while keeping all previously launched experiments. |

### How scheduled launches behave

* **Overlaps:** if the previous scheduled experiment is still running when the next slot arrives, Oqoqo skips that launch. After 3 consecutive skips, owners receive a **Schedule skipping launches** alert.
* **Notifications:** clean **Completed** runs (including rubric pass/fail results) send no completion notice; launches with run errors or failed Evals/Insights scoring send an in-app alert and at most one email per day per schedule. (To fail builds on pass-rate drops, run in CI with [`oqoqo results analyze`](https://docs.oqoqo.ai/operate/cli#run-an-experiment-in-ci).)
* **Lineage:** scheduled experiments display **From schedule** in **All experiments** and **Launched now from schedule** when triggered manually.

## When Oqoqo pauses a schedule

Oqoqo automatically pauses a schedule and marks it **Needs attention** if:

* A launch hits a blocker (disconnected provider, insufficient runs, or Agent mode disabled for the organization).
* A task, treatment, or model used by the experiment was deleted (select **Edit** to pick another experiment).
* Three scheduled launches fail in a row, or the user the schedule runs as leaves the organization.
* Another teammate edited a resource in a schedule that uses someone else's personal integration or MCP OAuth sign-in.

Fix the underlying issue—or select **Edit** to update the experiment—and select **Resume**. Schedule owners (the run-as user, creator, and last editor) receive a **Schedule paused** notification by email and in the app.

## Runs for scheduled launches

Oqoqo forecasts upcoming run demand across all active schedules in chronological order up to your next plan reset or expiration, so you see both **runs per launch** and **runs in the next 30 days** before creating or editing a schedule. If other launches spend your balance and leave a schedule short, Oqoqo sends **Schedule short of runs** before pausing at launch time.

## Who a schedule runs as

A schedule runs using the credentials and personal integrations of whoever created, resumed, or last edited its cadence or experiment (**Resume as you** when taking over another member's schedule). **Launch now** always runs as the person selecting it.

If a schedule uses a member's personal integration or MCP OAuth account and a teammate edits any task, file, machine, tool, treatment, or custom agent it launches, Oqoqo pauses the schedule for review. This prevents someone from launching experiments under another person's personal account unexpectedly.

## Delete a schedule

Deleting a schedule keeps all experiments it already launched. Conversely, deleting the source experiment of a schedule also deletes the schedule (the delete preview warns you first).

> [tab] Dashboard
>
> Open the schedule, open **⋯**, select **Delete**, and confirm.

> [tab] CLI
>
> ```bash theme={null}
> oqoqo schedules delete sch_c0a9f311 --lock-version 3
> ```
>
> See [`oqoqo schedules delete`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-delete).

> [tab] Plugin (MCP)
>
> Ask your AI assistant to delete the schedule; it calls **Delete a schedule** ([`delete_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#delete_schedule)) after your approval.

## From the CLI and the plugin

Always run `preview` before creating or updating a schedule, and pass the latest `lockVersion` on edits so concurrent changes do not overwrite each other.

| Task | CLI | Plugin (MCP) |
| - | - | - |
| List or inspect schedules | [`oqoqo schedules list`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-list), [`get`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-get) | [`list_schedules`](https://docs.oqoqo.ai/mcp-server/schedules#list_schedules), [`get_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#get_schedule) |
| Preview cadence and run forecast | [`oqoqo schedules preview`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-preview) | [`preview_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#preview_schedule) |
| Create, edit, pause, or resume | [`oqoqo schedules create`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-create), [`update`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-update), [`pause`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-pause), [`resume`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-resume) | [`manage_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#manage_schedule) |
| Launch immediately | [`oqoqo schedules launch`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-launch) | [`rerun_experiment`](https://docs.oqoqo.ai/mcp-server/experiments#rerun_experiment) (`schedule_id`) |
| Delete a schedule | [`oqoqo schedules delete`](https://docs.oqoqo.ai/cli/schedules#oqoqo-schedules-delete) | [`delete_schedule`](https://docs.oqoqo.ai/mcp-server/schedules#delete_schedule) |
| Filter experiments, runs, or frictions | `--schedule-id` on [`experiments list`](https://docs.oqoqo.ai/cli/experiments#oqoqo-experiments-list), [`runs list`](https://docs.oqoqo.ai/cli/runs#oqoqo-runs-list), [`frictions list`](https://docs.oqoqo.ai/cli/frictions#oqoqo-frictions-list) | `schedule_id` on [`list_experiments`](https://docs.oqoqo.ai/mcp-server/experiments#list_experiments), [`list_runs`](https://docs.oqoqo.ai/mcp-server/runs-and-results#list_runs), [`list_frictions`](https://docs.oqoqo.ai/mcp-server/frictions#list_frictions) |

## Next steps

> [card] [Track results over time](https://docs.oqoqo.ai/guides/track-agents-over-time.md)
>
> Use schedules to detect regressions and model drift.

> [card] [Launch an experiment](https://docs.oqoqo.ai/experiments/launch.md)
>
> Create the experiment that a schedule runs.

> [card] [Read results](https://docs.oqoqo.ai/evaluation/results.md)
>
> Compare pass rates across scheduled runs.

> [card] [oqoqo schedules](https://docs.oqoqo.ai/cli/schedules.md)
>
> Full reference for schedule flags and responses.


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