> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Schedules (Pro)
> Schedule Test Lists to run on a cadence — daily, weekly, monthly — with notifications on regressions.
Schedules let you run **automated test executions** at regular intervals. Instead of manually triggering runs, you set up a schedule that executes your Test Lists on a cadence, giving you **continuous monitoring** of your application's health.
**Schedules are a Pro feature.** Free-plan accounts have **0 schedule slots** — schedule creation is gated until you upgrade. **Starter** includes 5 schedule slots; **Standard** includes unlimited. See [Subscription Plans](/web-portal/admin/billing-and-plans).
## Key Benefits
* **Continuous Quality Assurance**: Automatically detect issues before they reach users. 24/7 monitoring and regression detection without manual effort.
* **Flexible Scheduling**: Recurring test executions with multiple scheduling options. Monitor run times and pause/modify schedules as needed.
* **Proactive Issue Detection**: Immediate notifications when tests fail. Track trends and identify performance degradation over time.
## Getting Started with Monitoring
### Prerequisites
Before setting up schedules:
* **[Create Test Lists](/web-portal/maintenance/test-lists)**: You need existing test lists to schedule
* **Verify Test Stability**: Ensure your tests run reliably
* **Set Up Notifications**: Configure how you want to receive alerts
* **Check Account Limits**: Verify your plan supports scheduling
### Steps
Go to Monitoring and click New Schedule to get started
Choose an existing test list to schedule
Review test cases and execution settings, and confirm test list is ready for automation.
Set **execution frequency** (daily, weekly, monthly), choose **specific times and days**, configure **timezone settings**, and set up **failure notifications**.
## Schedule Configuration
Configure when and how often your tests run automatically. Choose from multiple frequency options, set specific times and timezones, and customize scheduling patterns to match your monitoring needs.
### Frequency Options
Select how frequently your tests execute. Available options include hourly intervals, daily runs, weekly schedules on specific days, and monthly executions on set dates.
Choose how often your tests run automatically. Select from hourly, daily, weekly, or monthly scheduling patterns.
| Frequency Options | Description |
| :----------------- | :------------------------------------------- |
| Hourly | Execute tests every N hours |
| Daily | Execute tests every day at specified time |
| Weekly | Run tests on specific days of the week |
| Monthly | Schedule tests for specific dates each month |
Real-world examples showing how to configure different schedule types with specific times and timezones.
```yaml expandable theme={null}
Daily Schedule:
Time: 06:00 AM UTC
Frequency: Every day
Weekly Schedule:
Days: Monday, Wednesday, Friday
Time: 09:00 AM EST
Monthly Schedule:
Date: 1st of every month
Time: 12:00 PM PST
```
### Timezone Settings
Configure the timezone for your scheduled test executions. All schedules use **UTC by default**. You can specify different timezones to match your local time or business hours.
**Timezone Best Practices:** Convert your **local time to UTC** for accurate scheduling. Consider **daylight saving time changes** that may affect execution times. Use a **consistent timezone** across your team to avoid confusion.
## Managing Schedules
Once schedules are created, you can monitor their execution, view detailed status information, and manage them through the schedule dashboard. Track execution history, pause or modify schedules as needed, and ensure your monitoring runs smoothly.
### Reviewing Run-over-Run Changes
When you open a schedule, the executions table includes a **Changes** column that compares each run to the previous one and surfaces only the tests whose status changed:
* **Newly failed** test names appear as red chips — tests that passed last time but failed or got blocked this time
* **Newly recovered** test names appear as green chips — tests that failed or were blocked last time and pass now
Up to three names show per row, with `+N more` for longer lists. Runs with no status changes show `—`. This makes regressions and recoveries visible at a glance without opening each run.
### Schedule Dashboard
The Schedule Dashboard provides a comprehensive overview of all your automated test schedules, allowing you to monitor their status, execution history, and upcoming runs at a glance.
| Overview Information | Description |
| :-------------------------- | :----------------------------------------------------------- |
| Schedule Name | Descriptive name for the scheduled execution |
| Test List Name | Associated test list that will be executed |
| Recent Execution | Result of the most recent execution |
| Recurring | How often the schedule runs (hourly, daily, weekly, monthly) |
| Next Run | When the next execution is scheduled |
| Schedule Status | Current schedule status (Active, Paused, Finished) |
### Schedule Actions
Manage your test schedules with these available actions. Each schedule can be controlled individually to fit your testing workflow and requirements.
| Action | Description |
| :-------------------- | :----------------------------------------- |
| Edit | Modify timing and configuration |
| Deactivate | Stop a schedule from running going forward |