Troubleshooting · Troubleshooting
How to Fix WP-Cron Not Running in WordPress
Short answer
WP-Cron is not a clock: it checks for due work only when a page loads, so a quiet site runs scheduled posts and jobs late or not at all. Run wp cron test to check the trigger, then add define('DISABLE_WP_CRON', true); to wp-config.php and call wp-cron.php from a real system cron every five minutes.
Key takeaways
- WP-Cron runs due work only when a page loads; it is not a background service.
- wp cron test reports whether WordPress can trigger WP-Cron over HTTP.
- DISABLE_WP_CRON set without a system cron stops all scheduled work.
- A system cron calling wp-cron.php every five minutes is the lasting fix.
- WP Crontrol shows every scheduled event, its next run time, and missed items.
- Fixing cron does not publish posts that already missed their slot; run those by hand.
What is WP-Cron and why does it stop?
WP-Cron is WordPress's built-in scheduler, and it only checks for due work when a page loads.
The Plugin Handbook puts it plainly: "WP-Cron does not run constantly as the system cron does; it is only triggered on page load." That means a post set for 2:00 PM runs at 5:00 PM if nobody visits until then.
Three things stop it most often: nobody visits, the loopback request to wp-cron.php is blocked, or DISABLE_WP_CRON was set with no replacement.
WP-Cron handles scheduled posts, update checks, and plugin jobs such as backups and subscription renewals. When it stops, all of them wait silently.
WordPress ships with hourly, twice-daily, and daily recurrences, and plugins can register their own. The Scheduling WP Cron Events guide shows how wp_schedule_event() books a hook to one of those recurrences.
| Symptom | Most likely cause | First check |
|---|---|---|
| Posts sit past their publish time | No visits trigger WP-Cron | Run wp cron test |
| Backups never start | DISABLE_WP_CRON is set with no system job | Search wp-config.php for the constant |
| Plugin queues keep growing | The loopback request is blocked | Check Site Health and the host firewall |
| Events run hours late | Traffic is thin at night | Add a system cron |
How do you know WP-Cron is not running?
Scheduled posts sit past their time, backups never start, and plugin queues grow while the site looks fine.
Open Cron > Cron Events after installing WP Crontrol. It lists every event with its next run time, and warns you about events that missed their schedule. WP Crontrol also shows a warning when it detects a problem with your cron system.
A scheduled post that never goes out is the most visible sign. See How to Fix “Missed Schedule” on Scheduled Posts in WordPress for the post side of the same problem.
WooCommerce stores feel it in Action Scheduler: orders and renewals queue behind the same broken trigger. See How to Fix Past-Due Actions in the WooCommerce Action Scheduler.
A single missed post can also come from a bad publish time or a stuck draft, so check the queue before blaming cron.
How do you test WP-Cron with WP-CLI?
Run wp cron test from the site folder: it tries to trigger WP-Cron over HTTP and reports what happens.
The wp cron test command errors when DISABLE_WP_CRON is set, warns when ALTERNATE_WP_CRON is set, and warns on any non-200 response. A pass means the trigger works and the queue is the problem.
List the queue with wp cron event list to see each hook and its next run time. Anything hours overdue with a passing test means nothing is visiting the site.
If WP-CLI is not installed, the WP-CLI install guide says it needs PHP 7.2.24 or later and no other requirements beyond WordPress itself.
wp cron test
wp cron event list --fields=hook,next_run_gmt,recurrence
wp cron event run --due-now
What does DISABLE_WP_CRON do?
It stops WordPress from triggering WP-Cron on page loads, and nothing else.
Add define( 'DISABLE_WP_CRON', true ); to wp-config.php above the stop-editing line. The Hooking WP-Cron Into the System Task Scheduler guide shows the same line and explains that WordPress keeps running WP-Cron on page loads until you add it.
The constant alone is an off switch, not a fix. With no system job behind it, scheduled posts, update checks, and plugin queues all stop.
Direct calls to wp-cron.php still work with the constant set. That split is what makes the system-cron fix possible.
How do you replace WP-Cron with a real system cron?
Add the constant to wp-config.php, then have the server call wp-cron.php every five minutes.
WordPress's handbook gives the shape of the job: 0 0 * wget --delete-after http://YOUR_SITE_URL/wp-cron.php runs it once an hour. The Hooking WP-Cron Into the System Task Scheduler guide uses wget because most servers already have it.
Every five minutes is a safer interval than once an hour for posts and renewals. Change the first two fields to /5 * and keep the rest the same.
With WP-CLI on the server, run due events directly instead: wp cron event run --due-now skips the HTTP loopback entirely. The wp cron command page lists test, run, and delete among its subcommands.
Create the system job first, then add the constant. Adding the constant first leaves a gap where nothing runs at all.
How do you set up the system cron in cPanel?
Use the Cron Jobs tool in cPanel to call wp-cron.php on a timer, without touching the server shell.
Set the command to wget --delete-after https://example.com/wp-cron.php with your own domain in place of example.com, and run it every five minutes. WordPress's handbook page gives that wget form for Linux and macOS servers.
Add the DISABLE_WP_CRON line to wp-config.php only after the cPanel job exists. The job does the work; the constant only stops page loads from doing it too.
Many hosts also offer their own scheduler screen or a one-click WP-Cron tool. The steps differ by host, so use the host's own cron guide for the exact screen.
How do you check the fix worked?
Watch the next scheduled item: a post set for a few minutes ahead should publish on time.
Run wp cron event list again and confirm nothing stays overdue. WP Crontrol's usage docs show the same list inside the admin, under Cron > Cron Events.
Run wp cron test once more: it should now error, since DISABLE_WP_CRON is set on purpose. That error is expected, not a fault.
Scheduled backups are a good test, since they only run on cron. If a backup still never starts, see How to Fix a Failed UpdraftPlus Backup.
Fixing cron does not publish posts that already missed their slot. Open each missed post and publish it by hand, or reschedule it.
WP Crontrol 2.0.0, released 15 October 2026, made event logging free for everyone, so you can watch one event run and see its duration and errors.
When should you call your host?
Call the host when the loopback test fails and you cannot find the block yourself.
Hosts often block a server from calling its own URL, or they already run a system cron for you. Ask whether they run wp-cron.php for you before you add your own job.
Some managed hosts set DISABLE_WP_CRON for you and run the system job themselves. Adding a second job in that case only doubles the work.
If wp cron test fails with a connection error, the server may not resolve its own hostname. That is a host-side DNS or firewall setting, not a WordPress setting.
If the host runs a server firewall that blocks loopbacks, no WordPress setting can fix it. The loopback is a plain HTTP request from the server to itself, so the fix sits in the firewall rules, not in a plugin.
What mistakes should you avoid?
Do not set DISABLE_WP_CRON without a system job, and do not run the job once an hour for time-sensitive work.
- Setting the constant and stopping there: every scheduled task pauses with no error.
- Adding the constant below the stop-editing line: WordPress never reads it there.
- Calling the staging URL by mistake: the system job must target the live site.
- Using wp cron event run --all for a quick test: it fires every event, including heavy ones.
- Forgetting the missed posts: the fix only helps future schedules.
Frequently asked questions
Is it safe to disable WP-Cron?
Yes, as long as a real scheduler replaces it. Add the system cron job first, then set DISABLE_WP_CRON in wp-config.php. With no replacement, scheduled posts, update checks, and plugin jobs simply stop.
Why do scheduled posts still miss after I set up a system cron?
The job may target the wrong URL, run too rarely, or fail silently. Check the job's command and interval, confirm it hits the live site, and run wp cron event list to see whether events still sit overdue.
How often should the system cron run?
Every five minutes suits most sites: posts publish within five minutes of their time, and renewals and backups stay close to schedule. Once an hour is too slow for time-sensitive work.
What is ALTERNATE_WP_CRON?
It is a fallback that runs WP-Cron through a browser redirect instead of a loopback request. The wp cron test command warns when it is set. Use it only when loopbacks are blocked and you cannot run a system cron.
Does low traffic really break WP-Cron?
Yes. WP-Cron only checks for due work when a page loads, so a site with no visitors at night runs nothing until morning. A system cron removes the visit from the equation entirely.
Sources
- Hooking WP-Cron Into the System Task Scheduler WordPress Developer Resources
- Scheduling WP Cron Events WordPress Developer Resources
- wp cron test WordPress Developer Resources
- wp cron WordPress Developer Resources
- WP Crontrol WordPress.org
- How to use WP Crontrol WP Crontrol
- Installing WP-CLI Make WordPress
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
