# 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 most recent successful pings** (around the last ten), so you can always see the task is still reporting

For a healthy task that never fails, the log shows a short list of recent check-ins rather than one row per ping. You'll still be notified the moment 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](/docs/faq/what-timezone-is-your-server-configured-in) 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](/docs/features/cron-job-monitoring), confirm it appears in the log, and if anything looks wrong [get in touch](/contact).