# Schedules

See what runs on a timetable or when something happens, pause or run it, check its history, and switch on jobs modules offer.

Some work should happen without anyone pressing a button: a nightly sync, a summary every morning, a reply whenever a new request comes in. **Schedules** lists everything that runs by itself in your workspace, so you can pause it, run it now, see how it went, or switch on jobs your modules offer.

[Open Schedules now](/tenant/?open=settings/schedules)

## See what's scheduled

1. Open **System settings**, then **Schedules**.
2. Narrow the list with **All**, **Cron**, **Event**, **Manual**, **Module-managed** or **My schedules**.

Each card shows its name, whether it's **Active** or **Paused**, and when it runs:

| Trigger | Runs |
|---|---|
| **Cron** | On a timetable, such as every weekday at 8:00. |
| **Event** | When something happens, such as a new work order. |
| **Manual** | Only when someone runs it. |

**Managed by** a module means the module created it when you installed it.

## Pause, run or delete

1. Click a card. The **Detail** tab shows its trigger, when it runs, its timezone and where it came from.
2. Click **Run now**, **Pause** (or **Resume**) or **Delete**.

The **History** tab lists its recent runs and whether each one completed or failed. Deleting a schedule keeps its history.

## Switch on a job a module offers

Under **Offered by modules** you'll find jobs your modules include that aren't running yet: ones that ship switched off, and ones someone removed. Click **Turn on**. It runs as you.

## Create your own

1. Click **+ New** and choose **Agent on cron** (an agent does something on a timetable) or **Agent on event**.
2. Fill in a **Name**, the timetable or event, the agent's code, the person it acts as, and the **Prompt**: what you want the agent to do.
3. Click **Create schedule**.

The timetable is a cron expression: `0 8 * * *` means 8:00 every day. This form asks for codes rather than names, so if you're unsure what to enter, contact Data Visions support before you create one.

## Good to know

- **Only Workspace Admins** can open Schedules.
- **An agent schedule acts as the person named in it**, so pick someone whose role covers the job.
- **Fire event** sends a test event, so you can check an event schedule without waiting for the real thing.


Source: https://datavisions.ai/docs/system-settings/ai-and-automation/schedules
