WordPress: Missed schedule — scheduled posts not publishing (WP-Cron not running)
WP-Cron didn’t fire at the scheduled time, so scheduled posts and tasks (backups, emails, WooCommerce jobs) are late.
Seen on:
WordPress
Meaning
WP-Cron runs only when someone visits the site and requires loopback requests to work. Low traffic, DISABLE_WP_CRON without a real cron job, caching, basic auth or blocked loopbacks stop it.
Common causes
- Low traffic (no visits to trigger cron)
- DISABLE_WP_CRON true without a server cron
- Loopback requests blocked (firewall, basic auth, SSL)
- Full-page caching preventing PHP execution
⚡ Quick fix
- Disable WP-Cron and run it from system cron every 5 minutes
- Fix loopback requests (Site Health)
- Check scheduled events with WP Crontrol or wp cron event list
Detailed fix by platform
Linux
- bash
# crontab -e (as the web user) */5 * * * * cd /var/www/html && wp cron event run --due-now >/dev/null 2>&1
WordPress
define('DISABLE_WP_CRON', true); // only with the system cron above
How to diagnose
- Cron — wp cron event list
- Loopback — Site Health status
- Config — DISABLE_WP_CRON
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 403 Forbidden wp-admin WordPress: 403 Forbidden on wp-admin, wp-login.php or admin-ajax.php
- 404 except homepage WordPress: 404 Not Found on every page except the homepage (permalinks / .htaccess / Nginx rules)
- Another update is currently in progress WordPress: Another update is currently in progress.
Most viewed in WordPress
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026