New in QuietPulse: Second-Miss Alerts and Our Uneed Launch

A cron job that runs a little late can create an alert even when the next run succeeds. But delaying every alert can also hide a real failure. The right choice depends on what that job does.

QuietPulse now has an optional Wait for a second missed check-in before alerting setting for each job. It is off by default, so existing monitors keep their current alert timing.

How the optional setting works

After a successful heartbeat, QuietPulse normally sends the first missed-job notification when one expected interval plus the grace period has passed without another ping. With the new option enabled, the first notification waits until two intervals plus the grace period have passed since that successful ping.

For an hourly job with a five-minute grace period, that means the first notification moves from just after 65 minutes to just after 125 minutes without a ping. If a new heartbeat arrives before then, the clock starts again from that ping.

The job still appears as missing in the dashboard after the first deadline. The option delays the first notification, not the visible status. It also does not delay the alert for a newly created monitor that has never received its first heartbeat.

You can switch the option on or off when creating or editing a job in the dashboard. No change to your ping URL or cron command is needed.

When to use it — and when not to

This is useful for a low-risk task where one missed run is tolerable and the next run often catches up. It is not a substitute for setting an accurate interval and grace period. If your job runs at unpredictable times, fix those settings first.

Leave the option off for backups, billing, and other work where a single missed run needs prompt attention. Delaying an alert by a whole interval is a real trade-off, not free noise reduction. Our cron job monitoring best practices guide explains how to choose an interval, grace period, and alert route.

QuietPulse launched on Uneed

We also launched QuietPulse on Uneed on October 11, 2026. The listing describes the same core idea behind the product: send a heartbeat after a scheduled job finishes and get notified when the expected check-in does not arrive.

If you use QuietPulse, feedback on the Uneed page is welcome. In particular, tell us which scheduled jobs need immediate alerts and which ones benefit from a little tolerance. That distinction helps us make alerting useful without hiding failures.

Want to try the new option? Open your dashboard, edit a job, and choose the alert timing that matches the cost of missing one run.