Schedules and timezones

Check	Scheduling
Heartbeat	Expected interval or cron in the selected timezone
Website, DNS, TCP	Automatic interval with a plan-dependent floor
Domain, SSL certificate	Automatic hourly lookup

Interval expectations

For heartbeats, the next deadline is receipt time plus the interval. A grace period adds tolerance before an established location is marked late. It does not make a failing numeric value healthy.

Use an interval comfortably longer than the normal gap between successful reports. For a job that runs every hour but can take several minutes, choose a grace buffer consistent with the runtime rather than sending success before the job finishes.

For active probes, the interval controls scheduling, not a guaranteed real-time execution SLA. Queuing and lookup time can affect when a result arrives. Use the actual interval minimum shown for your account.

Cron expectations

Cron is available for heartbeats only. 0 * * * * expects the next hourly occurrence; 0 2 * * * expects the next 02:00 occurrence in the chosen timezone. Match the job’s timezone, including daylight-saving behavior. UTC avoids seasonal local-time shifts.

This example expects a daily 02:00 completion in UTC. The timezone selection is an unsaved illustration; choose the timezone used by your actual job.

The next occurrence is calculated after a received heartbeat. If a job’s completion crosses a scheduled boundary, inspect the next deadline shown in the app rather than assuming interval-style timing.

Check schedules are separate from notification recipient schedules. Suppressing a recipient outside working hours does not stop the check.