Silence is an alert.
Cronwize tells you when a scheduled job does not run on time. It reads Unix, Spring and Quartz cron as written and alerts by email, Slack, webhook or phone push.
At 02:00 every day. No account needed: you get a working ping URL right away.
Set up before the expression is cold.
Paste the schedule
From your crontab, a Spring @Scheduled annotation or the Cron explainer. Cronwize creates the monitor at once.
Add one line to the job
backup.sh && curl -fsS https://ping.cronwize.com/3f9a…
Hear about the run that did not happen
If the ping is late past the grace period, or the job reports a failure, the alert arrives with the expected time, the last ping and the job's output.
Reads cron the way you wrote it.
Paste a Spring or Quartz expression unchanged. Seconds fields, ?, L, W and # all work.
No false alarms from our downtime. No silent misses.
If Cronwize was down, your job is not blamed
Cronwize records every minute it could receive pings. A run that fell into its own outage is skipped and marked in the history, not turned into a 3 a.m. alert.
pg_dump: error: connection to server at "db.internal" (10.0.4.21), port 5432 failed: Connection refused
The failure is in the alert
Send the job's output with /fail and the first 500 characters arrive with the alert, so you can tell at a glance whether it waits until morning.
Every channel on every plan.
Alerts are the point of a monitor, so none of them are paywalled. Pro buys capacity and history, not the ability to be told.