Schedules
Automatically run checks at set intervals — no manual triggers needed. Schedules are available on Pro and Business plans.
Plan availability
| Plan | Schedules | Custom cron |
|---|---|---|
| Starter | Not available | — |
| Pro | ✅ Yes | Presets only |
| Business | ✅ Yes | ✅ Custom cron supported |
Starter plan users see an upgrade prompt instead of the schedule controls.
Adding a schedule Starter+
- On the project page, find the Scheduled Checks block below the action buttons.
- Click Add schedule.
- Choose a mode:
- Preset — pick from built-in frequencies
- Custom cron — enter any cron expression Business
- Select a frequency (Preset mode):
| Preset | Schedule |
|---|---|
| Daily (midnight UTC) | 0 0 * * * |
| Twice daily (00:00/12:00) | 0 0,12 * * * |
| Weekly (Monday midnight) | 0 0 * * 1 |
- For Custom cron: enter the expression in
minute hour day month weekdayformat (e.g.0 3 * * *). A minimum interval applies per plan. - Select a timezone from the dropdown (UTC, Europe/Warsaw, Europe/London, Europe/Berlin, America/New_York, America/Los_Angeles, Asia/Tokyo, Asia/Singapore).
- Click Save.
Schedule cards
Each schedule is shown as a card with:
- Frequency (preset name or cron expression)
- Timezone
- Next run — date and time of the next trigger (active schedules only)
- Last run — date and time of the most recent trigger
- Status badge: Active (green) or Paused (grey)
Action buttons on each card
| Button | Action |
|---|---|
| Edit | Change frequency or timezone |
| Pause / Resume | Toggle the schedule on or off |
| Runs | View the run history for this schedule |
| Delete the schedule (requires confirmation) |
Daily (midnight UTC)
Timezone: UTC
Next run: 27 May 2026, 00:00 UTC
Last run: 26 May 2026, 00:02
Run history
Click Runs on a schedule card to open the run history dialog. Each entry shows the date/time and a status badge:
| Status | Meaning |
|---|---|
| Triggered | A check was successfully started |
| Skipped (busy) | Skipped — a check was already running |
| Skipped (quota) | Skipped — weekly quota exhausted |
| Error | An error occurred when starting the check |
Scheduled checks run against active URLs only. Paused URLs are skipped.
If a check is already running when the schedule fires, the trigger is skipped (Skipped busy).
If the weekly quota is exhausted, the trigger is skipped (Skipped quota).
The slot counter (e.g. 1 / 3) in the block header shows how many schedules you have used.
Last updated July 20, 2026