Why is the cron log missing pings?
Don't panic: this is usually working as intended.
To keep the history readable, we periodically prune consecutive successful pings. What we keep:
- Every failure or missed event, in full
- The successful pings on either side of a failure, for context
- The latest two successful pings, so you can always see the task is still reporting
For a healthy task that has never failed, that means you'll see only a handful of entries in the log, even though we're recording every single ping as it arrives. You'll still be notified if a ping goes missing or arrives late.
When missing-ping alerts surprise you
If you're getting "missing ping" alerts but your job is definitely running, the most common cause is a timezone mismatch between your server and the monitor configuration. Check that the server's timezone matches what's set on the scheduled task in Oh Dear. Our timezone FAQ walks through how to check.
Finding the event log
Open the scheduled task detail page in Oh Dear. Scroll past the 30-day health chart and you'll find the full event log with every ping we've kept, including any custom payloads you sent along with them.
Still convinced something's off? Send us a test ping, confirm it appears in the log, and if anything looks wrong get in touch.
