Monitors
Monitors
Schedule recurring test runs to keep critical flows covered
Monitors run your tests on a schedule, so quality checks keep happening whether or not anyone remembers to start them.
In this section
- Scheduled Runs: configure recurring test runs on hourly, daily, or weekly schedules.
Monitors overview
Open Monitors in the sidebar to see every monitor in the project. Each row shows:
| Column | Meaning |
|---|---|
| Name | The monitor's name |
| Triggers | How many scheduled triggers the monitor has |
| Environment | The environment its runs target |
| Next Run | When the next execution fires, shown in the schedule's timezone |
| Status | Enabled or Disabled |
From the table you can open a monitor to edit it or delete it. Disabled monitors stay in the list but don't trigger runs.
A monitor executes selected published test cases against a chosen environment on its schedule. Every execution it triggers shows up in Runs like any other test run, so results, logs, and notifications all work the same way.