Scheduled tasks are delayed or no longer leaving.
Probable causes
- DISABLE_WP_CRON
- low traffic
- cron loop
Verifications.
- Limit the impact. — Identify whether an endpoint, service, or whole site is affected.
- Collect evidence. — Keep the exact error message, timestamp, and associated logs.
- Test the simplest hypothesis first. — Compare the affected system with a known-good path.
- Correct the confirmed cause and validate the result. — Apply one controlled change at a time and retest.
Solutions.
- Correct the confirmed cause rather than the symptom.
- Document the change and its result.
- Establish monitoring if the fault can recur.
When to escalate?
Escalate if the impact expands, data are at risk, or remediation requires an irreversible change.
WordPress scheduled-task focus
WP-Cron is normally triggered by web requests, so low traffic, blocked loopback requests or an intentionally disabled WP-Cron can leave scheduled actions overdue. First determine whether the site relies on visitor-triggered WP-Cron or a real server cron job.
What to verify
- Check whether WP-Cron is disabled in configuration and, if so, confirm that a server-side scheduler calls it reliably.
- Review Site Health and loopback behavior for requests that WordPress cannot make to itself.
- Inspect the scheduled-event queue and identify one plugin or task that is repeatedly failing or holding the queue.
- Check caching, security or maintenance rules that may block the cron endpoint.
Resolution path
Restore one reliable trigger model: either functioning WP-Cron or a properly scheduled system task. Correct the plugin-specific failure separately if one event keeps returning.
Validation
Watch an overdue event execute, confirm its next recurrence is scheduled correctly, and verify that the queue no longer accumulates delayed tasks.