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

# Test Scheduler

Use **Test Scheduler** to run supported Cloud Agent and Enterprise Agent tests during the periods that matter most. Define a recurring run window, use a faster interval during part of that window, and set a future time when ThousandEyes disables the test. A saved schedule keeps coverage aligned with operational hours and makes planned data gaps explicit.

This article explains how to create, confirm, change, and remove a test schedule.

## Before You Begin

Before you add a recurring schedule, check the following requirements:

| Requirement              | Details                                                                                                                                                                                                                                                                                                                                 |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Supported tests          | API, agent-to-agent, agent-to-server, DNS server, DNS trace, DNSSEC, FTP server, HTTP server, page load, RADIUS, RTP stream, SIP server, and transaction tests. The **Test Scheduler** section appears only for supported configurations. For an RTP stream test, scheduling controls are unavailable while continuous mode is on.      |
| Enterprise Agent version | Each selected Enterprise Agent with a recognized version must run version 1.243.0 or later. Upgrade incompatible agents before you save the schedule.                                                                                                                                                                                   |
| Base interval            | Select an **Interval** that is longer than any manual interval override you plan to use.                                                                                                                                                                                                                                                |
| Interval Boost           | Turn off **Interval Boost** before you add a recurring run window or manual interval override. Interval Boost and recurring schedules cannot be active together. To use automatic frequency changes based on issue probability instead, see [Interval Boost](https://docs.thousandeyes.com/product-documentation/tests/interval-boost). |
| Run window               | Plan one recurring run window. Its start and end must be on the same day and use five-minute increments.                                                                                                                                                                                                                                |

{% hint style="info" %}
In ThousandEyes for Government, you can configure a recurring run window and a manual interval override, but test expiration controls are not available.
{% endhint %}

## Understanding the Test Scheduler

The **Test Scheduler** combines the following settings:

| Setting                      | What It Controls                                                                                                                                                               |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Interval**                 | How often the test runs while it is enabled. This is the base interval.                                                                                                        |
| **Run on Days & Time**       | The days and daily time window when the test runs. No test data is expected outside this window.                                                                               |
| **Manual Interval Override** | A faster interval during selected days and times inside the main run window. The override interval must be shorter than the base interval.                                     |
| **Set expiration date**      | A future date and time when ThousandEyes disables the test. The expiration can be up to 10 years in the future.                                                                |
| Time zone                    | The IANA time zone used for the run window and expiration. If you do not select a specific time zone, the schedule uses the default time zone shown in **Advanced Scheduler**. |

Use a recurring run window or manual interval override when you know in advance when a test should run or run more often. To let ThousandEyes temporarily increase test frequency when issue probability rises, use [Interval Boost](https://docs.thousandeyes.com/product-documentation/tests/interval-boost) instead.

All schedule rules for a test use the same time zone. The schedule follows daylight saving time changes for that time zone. Changing your personal display time zone does not change the time zone saved with the schedule.

## Scheduling a Test

1. Go to **Network & App Synthetics > Test Settings**.
2. Create a supported test, or select the name of an existing test.
3. In **Test Scheduler**, select the base **Interval**.
4. Select **Edit schedule**.

   The **Advanced Scheduler** dialog opens. Changes in this dialog do not apply until you select **Save Schedule**.
5. To use a time zone other than the displayed default, turn on the time zone switch at the top of **Advanced Scheduler**, and select a time zone.
6. To disable the test automatically in the future, turn on **Set expiration date**, and set the **Expiration date** and **Expiration time**.

   The expiration must be in the future. It uses the effective schedule time zone.
7. Under **Run on Days & Time**, select **Every day**, **Weekdays**, **Weekends**, or **Custom...** from **Run on days**.
8. Under **During**, select one of the following options:

   * Select **All day** to run throughout each selected day.
   * Select **Set hours**, and enter the **Start time** and **End time** to create a daily window.

   The end time must be later than the start time on the same day. A window cannot cross midnight.
9. Optional: Under **Manual Interval Override**, turn on **Set interval override**, and complete the following settings:
   * Select an interval that is shorter than the base **Interval**.
   * Select days that are included in **Run on Days & Time**.
   * Select a time range that stays inside the main run window.
10. Select **Save Schedule**.

    The **Test Scheduler** summary shows the saved run window, expiration, override, and specific time zone, when present.
11. Save or deploy the test.

    The schedule starts controlling future test runs. No data is expected outside the recurring run window.

## Business-Hours Example

Suppose you want strong visibility during the workday without running the test overnight. Set the base **Interval** to 10 minutes, configure **Run on Days & Time** for weekdays from 08:00 to 18:00, and add a five-minute manual interval override from 09:00 to 17:00. The test then:

* Does not run outside the weekday 08:00–18:00 window.
* Runs every 10 minutes from 08:00–09:00 and 17:00–18:00.
* Runs every five minutes from 09:00–17:00.

This schedule strengthens coverage during the busiest hours while keeping planned gaps predictable. Review [About Units](https://docs.thousandeyes.com/product-documentation/user-management/usage-and-billing/about-usage-units) before changing intervals because more frequent test runs can increase unit use.

## Reviewing a Saved Schedule

Go to **Network & App Synthetics > Test Settings** to confirm the schedule:

* The **Effective Schedule** column shows the recurring days and times. Its time zone indicator shows when the schedule uses a time zone that differs from your current display time zone.
* The **Expiration** column shows the expiration date and time. It also identifies tests that expire within 30 days or have expired.
* The **Interval** column shows the base interval and any manual override.
* The **Status** column identifies an expired test.

If these columns are hidden, select the gear icon above the table, add **Effective Schedule** and **Expiration**, and save the column settings.

Use the **Schedule** filter to find tests that run every day, on weekdays, on weekends, or on an exact set of custom days. Use the **Expiration** filter to find tests with no expiration date, tests that expire in 31 or more days, tests that expire within the next 30 days, or expired tests.

## Changing or Removing a Schedule

1. Go to **Network & App Synthetics > Test Settings**, and select the test name.
2. In **Test Scheduler**, select **Edit schedule**.
3. Make any of the following changes:
   * To remove the recurring run window, select **Every day** and **All day**.
   * To remove the manual interval override, turn off **Set interval override**.
   * To remove expiration, turn off **Set expiration date**.
   * To move all rules to another time zone, update the schedule time zone.
4. Select **Save Schedule**, and save the test.

   If the test already expired, remove or move the expiration and then enable the test when you are ready to resume monitoring.

## Troubleshooting Test Schedules

| Problem                                                        | What to Check                                                                                                                                                                            |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Scheduler** does not appear.                            | Confirm that the test type supports scheduling and that **Test Scheduler** is available to your organization. For an RTP stream test, turn off continuous mode.                          |
| The schedule reports that an Enterprise Agent is incompatible. | Upgrade every selected incompatible Enterprise Agent to version 1.243.0 or later, and save the test again. Include every member of a selected Enterprise Agent cluster.                  |
| The run window does not save.                                  | Select at least one day. Use five-minute increments, and set an end time that is later than the start time on the same day.                                                              |
| The manual interval override does not save.                    | Turn off **Interval Boost**, select an interval shorter than the base interval, and keep the override days and times inside the main run window.                                         |
| The test runs at an unexpected local time.                     | Open **Advanced Scheduler**, and check the schedule time zone. If no specific time zone is selected, check the displayed default. Account for daylight saving time changes in that zone. |
| Results contain regular gaps.                                  | Compare the gaps with **Effective Schedule**. Missing results outside the configured run window are expected.                                                                            |
| The test is disabled and marked expired.                       | Check the **Expiration** column. Edit or remove the expiration, save the test, and enable it when you are ready to resume monitoring.                                                    |
