WP-Cron runs too frequently

Problem Summary

WP-Cron runs too frequently when scheduled tasks are triggered more often than the site or server needs.

Performance Impact

• Repeated backend work: Frequent cron runs consume PHP and database resources
• Slower uncached requests: Visitor-triggered cron can add work to page loads
• Log noise: High-frequency jobs make failures harder to spot
• Resource spikes: Multiple due events can run together

How to Detect

1. WP-CLI: Run wp cron event list --fields=hook,next_run,recurrence
2. Access logs: Check how often wp-cron.php is requested
3. Plugin settings: Review sync, cleanup, and reporting intervals

Solutions

1. Use Server Cron at a Sensible Interval

For many sites, every five or ten minutes is enough.

2. Reduce Aggressive Plugin Schedules

Imports, email syncs, analytics, and cleanup jobs should not run every minute without reason.

3. Remove Orphaned Hooks

Clear scheduled events left by deleted plugins.

4. Move Heavy Work to Queues

Large jobs should run predictably and avoid blocking normal traffic.