# Schedule runs

Scheduled runs let TestVibe execute selected tests on a recurring cadence without starting each run manually.

Use schedules for smoke checks, overnight regression coverage, staging environment monitoring, or any test set that should run at a predictable time.

## Create a scheduled run

1. Open **Schedule**.
2. Enter a schedule name.
3. Choose a **Frequency**.
4. Choose the **Site URL** source.
5. Select the groups or tests to include.
6. Choose one or more run configurations.
7. Leave **Enabled** on if the schedule should start running.
8. Save the schedule.

TestVibe stores the schedule in your repository and creates the GitHub workflow needed to run it.

## Frequency options

Available presets may include:

| Frequency           | Use it for                                             |
| ------------------- | ------------------------------------------------------ |
| Hourly              | Fast feedback for highly active test environments.     |
| Every 6 hours       | Regular daytime monitoring without running constantly. |
| Daily at 9:00 AM    | A morning health check for the team.                   |
| Weekdays at 9:00 AM | Business-day validation.                               |
| Mondays at 9:00 AM  | Weekly regression checks.                              |
| Fridays at noon     | End-of-week confidence checks.                         |
| Manual only         | Keep the definition available without automatic runs.  |

## Choose what the schedule runs

Schedules can target all groups or a selected subset. If no group is selected, TestVibe treats the schedule as an all-groups run.

Choose the smallest useful scope:

| Scope          | Best for                                                    |
| -------------- | ----------------------------------------------------------- |
| One group      | Monitoring a critical workflow such as sign-in or checkout. |
| Several groups | Daily confidence for the main product paths.                |
| Full suite     | Broad regression coverage on a slower cadence.              |

## Site URL source

A schedule can use:

| Source              | When to use it                                                 |
| ------------------- | -------------------------------------------------------------- |
| Explicit URL        | The schedule should always run against a specific environment. |
| Repository homepage | The repository already defines the correct app URL.            |

Use explicit URLs for staging, QA, preview, or dedicated test environments.

## Run now

Use **Run now** to start the schedule immediately without waiting for the next planned time. This is useful after creating or editing a schedule because it confirms the selected tests, URL, runner, and configuration work together.

## Active-run behavior

Scheduled runs are designed to avoid overlapping work. If a previous scheduled run is still active, the next scheduled attempt may be skipped instead of starting another copy of the same run.

For runner availability, see [Choose a runner](/runners/choose-a-runner.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/run-tests/schedule-runs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.