5. Over‑Aggressive Caching or CDN

Page‑cache plugins (e.g., WP Rocket, W3 Total Cache) often set WP_CACHE to true, which can bypass the PHP execution path needed for WP‑Cron unless you add an exception.

Quick Diagnostic Checklist

🔧 Quick Tip: Before making any changes, create a fresh database backup. A single mis‑step in the wp_options table can break scheduled tasks site‑wide.

1. Confirm WP‑Cron Is Enabled
   Open wp-config.php and look for define('DISABLE_WP_CRON', true);. If it exists, either remove it or set it to false for testing.
2. Trigger Manually
   Visit https://yourdomain.com/wp-cron.php?doing_wp_cron in a browser. A blank page with a 200 OK response indicates the script runs.
3. Check System Cron
   SSH into your server and run crontab -l. Verify that any WP‑Cron entry points to the correct URL and uses the right PHP binary.
4. Inspect Plugin Scheduler Logs
   If you use Action Scheduler (bundled with WooCommerce) or a similar library, view its log table (wp_actionscheduler_logs) for error messages.
5. Review Server Error Logs
   Look for PHP fatal errors or 500 responses around the time you attempted a manual trigger.

Effective Fixes to Restore WP‑Cron Functionality

1. Re‑Enable Traffic‑Based Cron (If Feasible)

If your site gets consistent traffic, simply removing DISABLE_WP_CRON often resolves the issue. Clear any page‑cache after the change so that the next visitor runs the cron.

2. Set Up a Reliable System Cron

For low‑traffic sites, a server‑level cron is the safest route. Add the following line to your crontab (replace example.com with your domain):

*/15 * * * * /usr/bin/curl -s https://example.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1

Make sure the PHP binary path matches your server’s configuration, and test it with crontab -e followed by sudo service cron restart.

3. Exempt WP‑Cron from Caching Layers

Most caching plugins let you add a “do not cache” rule. For example, in WP Rocket you can add wp-cron.php to the “Never Cache URLs” list. If you use a CDN, create a page rule that bypasses cache for /wp-cron.php.

4. Repair File Permissions

Run the following commands from your site’s root directory:

find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
chmod 644 wp-cron.php

This restores the typical WordPress permission set.

5. Isolate Problematic Plugins

Temporarily deactivate all plugins, then reactivate them one by one while monitoring the scheduler. Plugins that re‑introduce the issue should be replaced or patched.

6. Move to Managed WordPress Hosting for Built‑In Cron Reliability

If you’re juggling multiple fixes and still see intermittent failures, consider a hosting environment that handles cron jobs at the infrastructure level. Our WordPress Hosting service runs a dedicated server‑side scheduler, bypasses traffic‑dependent triggers, and integrates with automatic core updates—eliminating the most common WP‑Cron pitfalls.

7. Clean Up Stale Transients

After restoring cron, purge old transients to free database space. Run this WP‑CLI command:

wp transient delete --all

Or use a plugin like “Transients Manager” for a UI‑based cleanup.

Preventive Checklist for Future Cron Health

• Schedule a real system cron (every 15 minutes) and keep DISABLE_WP_CRON set to true.
• Whitelist /wp-cron.php in every caching plugin and CDN configuration.
• Monitor the wp_options table size; a sudden jump often signals a stuck cron.
• Enable WP‑CLI health checks (wp cron event list) as part of your regular maintenance routine.
• Keep plugins and themes up to date; outdated code is a frequent source of fatal errors that abort scheduled tasks.

Conclusion

WP‑Cron is a simple yet powerful scheduler, but its reliance on site traffic or misconfigured server cron jobs can cause silent failures. By recognizing the tell‑tale symptoms, running a focused diagnostic checklist, and applying the fixes above—especially moving to a managed WordPress environment when appropriate—you’ll keep scheduled tasks running smoothly, improve site reliability, and free yourself from chasing phantom bugs.