WordPress Scheduled Posts and Backups Not Running? WP-Cron Is Probably Broken
How to diagnose and fix WP-Cron issues that stop scheduled posts, backups, emails, and automations.
/ Direct answer
WP-Cron is WordPress’s built-in scheduler. If scheduled posts, backups, emails, or plugin jobs stop running, WP-Cron may be disabled, blocked, or not triggered often enough.
Why this happens
WP-Cron is not the same as a true server scheduler. By default, it runs when visitors hit the site. That can work for busy sites, but it becomes unreliable when traffic is low, caching is aggressive, or server rules block loopback requests.
Symptoms
WP-Cron problems often look unrelated until you see the pattern.
- Scheduled posts miss their publish time.
- Backups stop running.
- Subscription renewals or plugin jobs are delayed.
- Queued emails do not send.
- Security scans or reports stop arriving.
Recommended fix
For a business site, use a real server cron. That makes scheduled work predictable and removes the dependency on random visitors triggering WordPress at the right time.
Frequently asked questions
Is WP-Cron bad?
No. It is useful, but business-critical sites should not rely on visitor-triggered scheduling alone.
Can broken WP-Cron affect backups?
Yes. Many backup plugins rely on scheduled jobs, so cron issues can quietly stop backups.
Quick answer summary
/ Short answer
WP-Cron is WordPress’s built-in scheduler. If scheduled posts, backups, emails, or plugin jobs stop running, WP-Cron may be disabled, blocked, or not triggered often enough.
/ What matters most
- WP-Cron depends on site visits unless a real server cron is configured.
- Low-traffic sites and blocked loopback requests often expose the issue.
- The proper fix is usually a real server cron calling WordPress on a schedule.
/ Best next step
Match the support level to the real customer impact: leads, sales, bookings, logins, security, recovery, and trust. If the site creates money or customer confidence, choose ongoing care over occasional fixes.