Feature · Heartbeat Monitoring
The backup job that silently stopped running
Instead of AmICited probing your server, your scheduled job calls its own unique ping URL after every successful run. Miss the expected interval, plus a grace period, and an incident opens — catching the failures regular uptime checks can't see.
Heartbeats
Nightly backup
Every 1h
12m ago
Newsletter queue
Every 15m
2m ago
Data warehouse sync
Every 6h
9h ago
Your job calls its ping URL after every successful run — FlowHunt never has to probe your server.
A dead man's switch for your jobs
Silence is the alert
A cron job that crashes, a backup that stops running, an import that hangs — none of them hit a public endpoint a monitor could check. Heartbeats flip the model: your job proves it's alive, and AmICited only speaks up when it goes quiet.
- ✓Unique ping URL per job — one line added to the end of a script, no server-side probing required.
- ✓Expected interval and grace period — set how often the job should run and how much slack it gets before a miss counts.
- ✓Alerts to the right people — notification recipients configured per heartbeat, same as any other monitor.
- ✓Catches what uptime checks can't — nightly backups, scheduled imports and queue workers never get hit by a visitor request.
Upcoming maintenance windows
Planned database upgrade
Aug 22, 02:00–03:30 · All monitors
CDN migration
Sep 3, 22:00–00:00 · yoursite.com
Quarterly load test
Repeats · does not repeat · checkout only
Suppresses incident changes and uptime math during planned work only.
Planned work, excluded
Tell the system when a miss is expected
A heartbeat you deliberately paused for planned maintenance shouldn't open an incident. Schedule a Maintenance Window so both heartbeats and uptime monitors understand the gap is expected, not a failure.
- ✓Scope by domain or monitor — suppress exactly the checks affected by the planned work.
- ✓Recurring or one-off — a nightly deploy window or a single planned migration, either way.
- ✓SLA math stays honest — planned downtime never counts against your uptime target.
0
server probing required — your job does the talking
FlowHunt never has to guess whether a background job ran. The job calls its ping URL; silence past the grace period is the only signal that matters.
See Uptime Monitors
Ready to catch the job that silently stopped running?
Free check · 7-day trial · no credit card