Missed-Run Alerts

Failure alerts tell you when a request ran and failed. Missed-run alerts tell you when a run that shouldhave happened never did — the silent failure that's easy to miss. Available on Pro and Business.

How it works

Every active job has a next_run_at timestamp. If that time passes by more than 10 minutes without the job executing, QuzenixCron sends a missed-run alert. This usually means the scheduler was briefly unavailable or the job was stuck — exactly the kind of thing you want to know about.

Delivery

Alerts go to your account email and to any connected chat channels (Telegram, Slack, Discord). Each alert includes the job name, URL, and how many minutes overdue it is, with a direct link to the job.

One alert per hour, per job

Missed-run alerts have a 1-hour cooldown per job so a prolonged outage doesn't flood your inbox. Once the job runs again, the next missed run can alert fresh.

Missed-run vs. failure vs. heartbeat

Failure alert — the request ran but returned an error. Missed-run alert — the scheduled run never happened. Heartbeat alert — a service that pings you stopped pinging (see Heartbeat Monitors). Together they cover both directions of failure.

PreviousDiscord Notifications Next Response Assertions