---
title: "How do I manage Schedules?"
description: "TL;DR: Schedules are recurring timed runs of playbooks. View and manage all workspace schedules from Schedules in the sidebar, or configure a schedule trigger on an individual playbook. Each schedule shows its cron expression, next run time, and recent status."
canonical_url: "https://docs.ballet.dev/articles/how-do-i-manage-schedules-NTU9cNrk8w"
md_url: "https://docs.ballet.dev/articles/how-do-i-manage-schedules-NTU9cNrk8w.md"
---
# How do I manage Schedules?

**TL;DR:** Schedules are recurring timed runs of playbooks. View and manage all workspace schedules from **Schedules** in the sidebar, or configure a schedule trigger on an individual playbook. Each schedule shows its cron expression, next run time, and recent status.

## Who this is for

Builders who automate playbooks on a recurring basis.

## How do I create a schedule?

**Option 1 — From a playbook:**
1. Open the playbook's **Trigger** panel.
2. Select **Schedule**.
3. Set the cron expression or pick a preset (daily, weekly, etc.).
4. Save.

**Option 2 — From the Schedules page:**
1. Open **Schedules** from the sidebar.
2. View all scheduled playbooks across the workspace.

## How do I read the Schedules page?

The Schedules page shows:

- Playbook name
- Cron schedule
- Last run status
- Next scheduled run

## How do I pause or remove a schedule?

Edit the playbook's Trigger panel and switch back to Manual, or update the cron expression. Changes take effect on the next scheduled boundary.

## Tips for reliable schedules

- Test the playbook with a manual run before enabling a schedule.
- Use secrets for credentials — scheduled runs use the same connections as manual runs.
- Monitor the History tab for failed scheduled runs.

## Related articles

- [What triggers can start a playbook?](/articles/what-triggers-can-start-a-playbook-manual-schedule-webhook-P4mdwPZDGg)
- [How do I run a playbook?](/articles/how-do-i-run-a-playbook-dChtouCzok)
- [How do I read runs and run history?](/articles/how-do-i-read-runs-and-run-history-WukfYP5du3)