> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/running-tests/schedules.md).

# Schedules

Run BugBug suites in the cloud automatically: create a schedule, choose how often it runs (every minute to monthly), timezone, which profile is used, run a schedule now, notifications, limits and FAQ.

A schedule runs one or more [suites](https://docs.bugbug.io/organizing-tests/suites.md) [in the cloud](https://docs.bugbug.io/running-tests/in-cloud-on-server.md) at set times, for example every hour on production and once a night on staging. You don't need your computer or browser for it.

{% hint style="info" %}
**In short**

* Schedules run **suites**, not single tests. Put the tests you want to run into a suite first.
* How often: every 5 or 15 minutes, hourly, daily, weekly or monthly. **Every minute** is available on the Business plan.
* Times are in the project's timezone, set in [Project settings → General](https://docs.bugbug.io/preventing-failed-tests/project-settings.md#general).
* Scheduled runs are cloud runs: they use your [parallel runs](https://docs.bugbug.io/running-tests/parallel-mode.md) and appear in runs history.
* Schedules are available on all paid plans. See [pricing](https://bugbug.io/pricing/).
  {% endhint %}

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F9bl4qLUOtQmgKqx1Y4sb%2F3_meptyScreen.png?alt=media&amp;token=ffc7e243-f929-4b1d-bf2a-ef47aaa110a1" alt="Schedules page with no schedules"><figcaption><p>Schedules page</p></figcaption></figure>

## Create a schedule

1. Make sure the suite passes when you [run it in the cloud](https://docs.bugbug.io/running-tests/in-cloud-on-server.md).
2. Go to **Schedules** and click **New schedule**.
3. Enter a **Name**.
4. In **Time**, choose how often it runs and, for daily, weekly and monthly schedules, the day and hour.
5. In **Scheduled suites**, select one or more suites.
6. Make sure **Enabled** is on.
7. Click **Create schedule**.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FTLvb3quBjWTjMcA85mnJ%2Fnew_schedule_options_list.png?alt=media&amp;token=5a2deab2-f204-43ea-b4f9-8cb6bc90277e" alt="New schedule form"><figcaption><p>New schedule</p></figcaption></figure>

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FSYdSVwwJBKluXdQY2MgW%2F2_scheduleModal.png?alt=media&amp;token=ef66d8db-f2c4-4d35-92b8-348167c190ab" alt="New schedule form filled in"><figcaption><p>A schedule that runs every hour</p></figcaption></figure>

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2Fyyvs2dWQIB3wdHigvemT%2F1_schedule.png?alt=media&amp;token=b7dbddc8-c22d-466c-8934-d64e6de61fee" alt="Enabled schedule in the schedules list"><figcaption><p>Enabled schedule</p></figcaption></figure>

A schedule without suites can't be enabled.

## How often a schedule runs

| Option               | Runs                                               | Plans          |
| -------------------- | -------------------------------------------------- | -------------- |
| **Every minute**     | Every minute                                       | Business       |
| **Every 5 minutes**  | Every 5 minutes                                    | All paid plans |
| **Every 15 minutes** | Every 15 minutes                                   | All paid plans |
| **Hourly**           | Every hour                                         | All paid plans |
| **Daily**            | Every day at the chosen hour                       | All paid plans |
| **Weekly**           | On the chosen days of the week, at the chosen hour | All paid plans |
| **Monthly**          | On the chosen day of the month, at the chosen hour | All paid plans |

Custom cron expressions aren't supported.

* **Timezone.** You enter the hours in the project's timezone, not in your own: a schedule set to 9:00 in a project that uses UTC runs at 9:00 UTC, wherever you are. Change the timezone in [Project settings → General](https://docs.bugbug.io/preventing-failed-tests/project-settings.md#general). BugBug then converts the hours of existing schedules, so they keep running at the same moment.
* **Start time.** Every-minute, 5-minute and 15-minute schedules start on time. Hourly, daily, weekly and monthly runs can start a little later when many runs start at the same moment, so they're spread over the available cloud browsers.

## What a scheduled run does

* **Each selected suite runs in the cloud**, with the suite's own settings: its [profile](https://docs.bugbug.io/editing-tests/variables.md#profiles), its tests and whether it runs in parallel.
* **The tests use your parallel runs.** A schedule starts as many tests at once as your organization's [parallel runs](https://docs.bugbug.io/running-tests/parallel-mode.md) allow, shared with other cloud runs. The other tests wait in the queue.
* **The queue has a limit.** An organization can have up to 1000 tests queued or running in the cloud. If a scheduled run would go over it, the run fails without starting.
* **Results are in runs history.** Scheduled runs show **Scheduler** as their trigger in [runs history](https://docs.bugbug.io/debugging-tests/runs-history.md). The start and end times in the run's details are in the project's timezone. See [Dates and times](https://docs.bugbug.io/debugging-tests/runs-history.md#dates-and-times).

## Run a schedule now

To run all suites of a schedule right away, open the schedule's menu and click **Run in cloud**. A disabled schedule can't be run.

## Manage schedules

In the schedule's menu you can **Rename**, **Duplicate** or **Delete** it. To pause a schedule without deleting it, turn off **Enabled**.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FXVaeVrx3fFHT9NKL5fcN%2F5_schedulespageOverview.png?alt=media&amp;token=2b2e1af7-681b-41b8-ab1f-4efb46de38dc" alt="List of schedules"><figcaption><p>List of schedules</p></figcaption></figure>

Use several schedules to run different suites at different times, for example production tests every hour and the full regression on a [test environment](https://docs.bugbug.io/editing-tests/variables.md#work-with-different-development-environments) once a night.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FlXUPr4AcsqzXRC8sHQVR%2F4_newscheduleDaily.png?alt=media&amp;token=276c47fb-9792-45d2-bf63-e48cd4185361" alt="Suites selected for a daily schedule"><figcaption><p>Suites selected for a daily schedule</p></figcaption></figure>

## Notifications

By default, you get an email when tests in a scheduled run fail. Choose who gets notified, and when, in [Alerts](https://docs.bugbug.io/collaboration/alerts.md), for example only for failed runs or in [Slack](https://docs.bugbug.io/integrations/slack.md).

![Email notifications with different statuses](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F1pmN01MLwPRnDKYTltqc%2Femail%20notifications.png?alt=media\&token=fe628ce9-946f-482d-83f5-136aa89758e2)

The email has the results and links to the failed tests. A link opens a read-only report of the run from [runs history](https://docs.bugbug.io/debugging-tests/runs-history.md).

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F90llpevS86SoUvQU2LDC%2Femail_schedule1.png?alt=media&amp;token=f0accff2-f972-46a0-808e-90637275a699" alt="Email notification for a failed schedule"><figcaption><p>Email for a failed schedule</p></figcaption></figure>

{% hint style="info" %}
To avoid false alarms from flaky tests, turn on [auto-retry of failed cloud tests](https://docs.bugbug.io/organizing-tests/suites.md#auto-retry-failed-cloud-tests-to-prevent-flaky-tests-notifications) in your suites.
{% endhint %}

## FAQ

<details>

<summary>Can I schedule a single test?</summary>

No. Schedules run suites. Create a suite with that one test and schedule the suite.

</details>

<details>

<summary>Can I use a cron expression?</summary>

No. Choose one of the options: every minute (Business plan), every 5 or 15 minutes, hourly, daily, weekly or monthly.

</details>

<details>

<summary>Which timezone does a schedule use?</summary>

The project's timezone from **Project settings → General**. The default is UTC. You enter the schedule's hours in that timezone, not in your browser's timezone.

</details>

<details>

<summary>Does the project timezone change the time in the browser during a test?</summary>

No. The project timezone is used for schedules and for the times shown in run details. It doesn't change the browser's clock or timezone during a test, so `new Date()` in your code and the `timestamp` [variable](https://docs.bugbug.io/editing-tests/variables.md) aren't affected.

</details>

<details>

<summary>Which profile and variables does a scheduled run use?</summary>

Each suite runs with its own profile, set in the suite's settings. To run the same tests with other values, create another suite with another profile and add it to the schedule.

</details>

<details>

<summary>Why did my scheduled run start a few minutes late?</summary>

Hourly, daily, weekly and monthly runs are spread over the available cloud browsers when many runs start at the same time. The tests can also wait in the queue until one of your parallel runs is free.

</details>

<details>

<summary>Where does the "Default Schedule" come from?</summary>

During a trial, BugBug can create a **Default Schedule** after you record your first test. It runs the suite with all tests on two days of the month. You can change, disable or delete it.

</details>

<details>

<summary>Do schedules need my computer or the Chrome extension?</summary>

No. Scheduled runs run in BugBug's cloud.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/running-tests/schedules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
