# Schedules

Run your suites automatically on a cron schedule so regressions surface without anyone clicking Run.

<Mermaid chart={`flowchart LR
    S["+ Add Schedule"] --> B["Name & Agent"]
    B --> T["Trigger<br/>daily / weekly / cron"]
    T --> SC["Select Suites"]
    SC --> A["Schedule active"]
    style A fill:#1842ef,stroke:#1842ef,color:#ffffff
`} />

**Path:** Trust Lab → Schedules (fifth icon)

Schedules automate your test [suites](/user-guides/trust-lab/test-suites/) so regressions are caught without manual intervention.

## Creating a schedule

Click **+ Add Schedule**. The **Create Schedule** dialog has three sections:

**Schedule Basics**

- **Name**: a descriptive label for this schedule.
- **Agent**: which agent to run the tests against.

**Trigger Conditions**

- **Trigger Type**: currently supports **Recurring (Cron)**.
- **Schedule Pattern**: how often to run — Daily, Weekly, Hourly, or a custom cron expression.
- **Time**: what time to run (e.g., 02:00).
- **Timezone**: the timezone used to interpret the time (e.g., America/Los_Angeles).

A confirmation line previews the final schedule in plain English: "Runs daily at 02:00 America/Los_Angeles."

**Scope**

- **Suites**: choose which test suite(s) the schedule will run.

Click **Create** to activate the schedule.

## Schedule list columns

| Column | Description |
| :--- | :--- |
| **Name** | Schedule label |
| **Agent** | Which agent is being tested |
| **Trigger** | The cron expression |
| **Schedule** | Human-readable frequency |
| **Enabled** | Active or paused toggle |
| **Last Triggered** | When the schedule last fired |
| **Last Modified** | When the schedule config was last changed |

## Recommended schedules

- **Daily sanity check**: run your Sanity suite every day at 08:00 to start the day with a health snapshot.
- **Nightly regression**: run a comprehensive suite at 02:00 when traffic is low, so results are ready for morning review.
- **Post-deployment**: pair a webhook trigger with your CI/CD pipeline to run tests automatically after every production deploy.