A scheduled event has failed
“A scheduled event has failed” in WordPress Site Health: causes and what to check
Site Health shows this critical issue when a WP-Cron event ended with an error the last time it ran. A related notice, “A scheduled event is late,” appears when events are overdue. Both read from the same task list, stored in the cron option.
Which of these do you see?
A plugin task stops with an error, and the next run fails the same way.
WP-Cron is not running often enough, or the list is too long to finish.
Common causes
References
Rather not fix it yourself? Let WP119 handle it automatically.
Expired transients, piled-up scheduled tasks and a bloated scheduler table are all handled automatically: expired transients are cleared; overdue scheduled tasks are cleaned up (if your configuration disables the automatic scheduler, the report notes that they will pile up again); duplicate and flood events and completed store jobs are purged in batches, in place on your host. Autoload bloat is noted in the report and not touched. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when scheduled events keep failing or piling up and the site or the admin area slows down.
Check my site →