Schedules
A schedule defines when and where your monitors run. Without a schedule, a monitor is just a definition that you can trigger manually. Attaching a monitor to a schedule turns it into continuous, automated observability.
What a schedule controls
Each schedule has three settings:
- Frequency — how often each monitor runs, from once every few seconds (high-frequency tier) to once every 24 hours
- Region set — which geographic regions or cloud providers to draw nodes from (e.g., worldwide, a specific continent, or Amazon AWS locations only)
- Node selection mode — Worldwide (APIContext automatically rotates through all nodes in the region set) or Manual (you pick specific node locations)
When a schedule fires, APIContext selects a node from the configured region set and runs every monitor assigned to that schedule from that node. Over time, all nodes in the region set are used roughly equally, giving you geographic coverage without manual rotation.
Frequency tiers
| Interval | Availability |
|---|---|
| 1 second to 59 seconds | Contract tier with feature_highfreq entitlement |
| 1 minute to 24 hours | All tiers |
High-frequency monitoring is designed for latency-sensitive services where sub-minute resolution matters. It consumes quota proportionally — a 5-second interval uses 12x the quota of a 1-minute interval.
Schedules and downtimes
A schedule can have downtime windows that pause all its monitors during planned maintenance. Organization-wide downtimes pause every schedule across the organization. See Downtimes for details.
Default schedule
Every new project is created with a Default Schedule set to worldwide coverage at 5-minute intervals. You can edit or replace it at any time.
See also
- Run a monitor on demand — manual runs and scheduling walkthrough
- Setting and managing schedules — detailed schedule configuration
- Test node locations — the global node network your schedules draw from