A few improvements this week, most of them about getting the right alert to the right place. Everything below is live now.
Heartbeats for daily and weekly jobs. Heartbeat monitors used to top out at one check-in an hour, so a nightly backup or a weekly report couldn't be watched properly. Now a heartbeat can expect a check-in anywhere from every minute to every 7 days.
A grace period you choose. Set how late a check-in may be before the monitor goes down, from 1 minute to 24 hours. If you don't pick one, it uses a sensible default for the interval: 2 hours for a daily job, 6 hours for a weekly one. Existing heartbeats keep their current settings.
See how long your jobs take. Add /start to your heartbeat URL when a job begins, and call the plain URL when it finishes. The monitor shows how long each recent run took, so you can spot a backup slowly getting longer. You can also set a longest run time, and you're alerted if a run starts but doesn't finish in time. It's optional: jobs that only call the plain URL work exactly as before.
Alert addresses are confirmed before they get alerts. When you add an email address to a monitor, it gets one short email asking its owner to confirm. Until they do, it stays on your list but receives nothing. Your own account email, and every address you'd already added, keep working without any action.
A nudge to send alerts somewhere else. If every alert address on a monitor is on the same domain as the site you're watching, the monitor form now suggests adding one with another provider. When a site goes down, its own mailbox often goes with it.
Questions or anything that looks off: open a ticket from Support.
