WP-Cron Not Working: Scheduled Tasks Never Run (2026)

wp-cron isn't a real cron job - it's a timer that only fires when someone loads a page. That's why it fails two ways: silently on quiet sites (no visitors = no trigger) and destructively on busy ones (every visitor triggers a check, spawning concurrent runs that choke the server). The fix is the same: replace the pseudo-cron with a real one.

Symptoms: Is Your Cron Actually Broken?

• Scheduled posts showing "Missed schedule" (see the missed schedule guide)
• Backups, plugin updates, or stats jobs that silently skip
• WP Crontrol or Site Health shows events overdue by hours/days
• WooCommerce scheduled actions piling up unfinished

Step 1: Disable the Pseudo-Cron

In wp-config.php, above "That's all, stop editing":

This stops wp-cron firing on every pageview - which on a busy site was spawning overlapping runs. Now nothing triggers it. That's intentional; step 2 puts it on a real schedule.

Step 2: Set Up a Real Cron Job

In cPanel → Cron Jobs (or your host's equivalent), add:

Every 15 minutes works for most sites. For WooCommerce or heavy scheduling, go every 5. Your scheduled tasks now fire on a clock, not on traffic.

Step 3: Check for Blocks

If the real cron still fails: wp-cron.php is an HTTP request your server makes to itself - a "loopback" request. Security plugins, WAF rules, and hosts that block loopback connections kill it. Whitelist wp-cron.php in your firewall. Test manually: load https://yourdomain.com/wp-cron.php?doing_wp_cron in a browser - it should return a blank 200 page, not an error.

When wp-cron WAS the Problem All Along

On busy sites, the pseudo-cron was creating load: every pageview triggered a cron check, and heavy jobs (backups, WooCommerce) collided and ran concurrently - the same resource exhaustion behind 503 errors and 429 rate limits. DISABLE_WP_CRON + a real cron doesn't just fix schedules - it reduces server load measurably.

Keep Reading

• Missed schedule error - the scheduled-posts symptom
• 429 too many requests - when pseudo-cron causes rate limits
• 503 service unavailable
• Update failed - updates are cron-dependent too
• Bluehost review 2026
• WordPress Changes Not Saving: Updates Vanish After Publish (2026)