Skip to content
webfixed

Guides / WordPress

WP-Cron not running: scheduled posts and backups missed

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1.

Short answer

WP-Cron only runs when someone loads a page, so quiet sites, full-page caches and blocked requests to wp-cron.php leave scheduled posts and backups waiting. Check Tools, Site Health for a failed or late scheduled event. For a reliable fix, set up a server cron job that runs WP-Cron every few minutes, then add DISABLE_WP_CRON to wp-config.php.

Symptoms

You may see one of these messages:

Missed schedule

A scheduled event has failed

A scheduled event is late

Your site could not complete a loopback request

  • Scheduled posts stay unpublished, and the Posts list shows "Missed schedule" in the Date column.
  • Scheduled backups stop appearing in your backup plugin, or its next backup time never moves on.
  • Site Health reports "A scheduled event has failed" or "A scheduled event is late".
  • Update checks, cache clearing and other regular tasks happen late or not at all.
  • Things catch up when you visit the site yourself, then stall again.

Causes, most likely first

  1. Not enough visits

    WP-Cron is not a real timer. WordPress checks for due tasks on each page load, so on a quiet site a task waits for the next visit. WordPress’s own example is a task due at 2pm that runs at 5pm because no page was loaded in between.

  2. A full-page cache

    WordPress starts WP-Cron while it builds a page. When a caching plugin, the host or a content delivery network serves a saved copy instead, WordPress does not get that far, so the visit does not count.

  3. Requests to wp-cron.php are blocked

    To run tasks, WordPress sends a request from the server to its own wp-cron.php file. A firewall, a security plugin, a host rule or password protection on the whole site can refuse that request, and then nothing runs.

  4. DISABLE_WP_CRON with nothing to replace it

    When wp-config.php contains define( 'DISABLE_WP_CRON', true ); visits no longer start WP-Cron. That is fine with a server cron job in place, but the job is easy to lose in a move to a new host.

How to fix it

See what is overdue

Scheduled events are what publish scheduled posts on time, check for updates to WordPress, plugins and themes, and run tasks for plugins. Backup plugins that work to a timetable usually rely on them too.

  1. Open the Status tab. "A scheduled event has failed" or "A scheduled event is late" names the event that is overdue. Site Health also tests loopback requests, which WP-Cron needs.Menu: Tools > Site Health
  2. For a full list, install the free WP Crontrol plugin from wordpress.org. It lists every scheduled event, when each is next due, and flags events that have missed their schedule.
  3. Open WP Crontrol’s list of events. Tools, then Cron Events also works.Menu: Cron > Cron Events
  4. Open wp-config.php and search for DISABLE_WP_CRON. If it is set to true, visits do not start WP-Cron, and a server cron job must do it instead.
  5. If you have WP-CLI, run wp cron test. It reports "Success: WP-Cron spawning is working as expected." when all is well, and an error if DISABLE_WP_CRON is set.

Run WP-Cron from a server cron job

A cron job in your hosting control panel runs a command on a timetable, whether or not anyone visits. WordPress documents this as the way to hook WP-Cron into the server’s own scheduler.

  1. Find the cron jobs section of your hosting control panel. If there is not one, ask your host whether they can add a job for you.
  2. Add a job that requests your site’s wp-cron.php. WordPress’s example uses wget: wget --delete-after https://www.yourdomain.co.uk/wp-cron.php. The --delete-after part stops wget saving a copy of the reply each time.
  3. Curl does the same job if that is what your host provides. All it has to do is request the wp-cron.php address.
  4. If your host supports WP-CLI, the job can instead run wp cron event run --due-now from the site’s main folder. This runs every task that is due and avoids overlapping runs.
  5. Set the timetable. WordPress’s example runs every 15 minutes. Choose a shorter gap if scheduled posts must go out close to their time.
  6. Once the job has run and Site Health or WP Crontrol shows nothing overdue, add define( 'DISABLE_WP_CRON', true ); to wp-config.php, above the line that says "That's all, stop editing!". Visits then stop starting WP-Cron, and the server job does it instead.

Add DISABLE_WP_CRON only after the server job is working. With it set and no job in place, nothing scheduled runs at all.

Stop the request to wp-cron.php being blocked

  1. If the Status tab shows "Your site could not complete a loopback request", open that item to see the error it got.Menu: Tools > Site Health
  2. Check your security plugin, firewall and the host’s security settings for rules that block wp-cron.php or requests from the server’s own address, and allow them.
  3. Check that your content delivery network or firewall service does not challenge or block requests to wp-cron.php.
  4. If the whole site sits behind a password at server level, as staging sites often do, WordPress’s own request is refused too. Use a server cron job there instead.

Use ALTERNATE_WP_CRON only as a last resort

If the server cannot reach its own wp-cron.php and you cannot add a cron job, add define( 'ALTERNATE_WP_CRON', true ); to wp-config.php. WordPress then runs due tasks during a visitor’s own page load, by redirecting that visit to the same address with ?doing_wp_cron= and a number added. Visitors can see that in the address bar, and it still depends on visits, so it does not help a quiet site. WordPress’s documentation notes that this method has certain risks.

  1. Add the line above the "That's all, stop editing!" line in wp-config.php.
  2. Load a page on the site, then check Site Health or WP Crontrol for overdue events.
  3. Remove the line again once you have a server cron job.

Catch up on what was missed

  1. When WP-Cron runs again, WordPress runs overdue tasks at the next opportunity, including posts marked Missed schedule.
  2. In WP Crontrol you can run an overdue event straight away instead of waiting.
  3. Check your backup plugin’s log for the backups that did not run, and start one by hand once the schedule is working.

If that didn’t work

  1. The server job runs but fails

    If your hosting panel can email the output of a cron job, turn that on. An error in the output, such as a refused connection or a request for a password, shows the request is being blocked.

  2. One event keeps failing

    If Site Health keeps naming the same event, it may belong to a plugin you have removed, or its task may crash each time. WP Crontrol shows which plugin the event belongs to.

  3. A plugin queue is still behind

    Action Scheduler, a task queue that handles jobs such as WooCommerce webhooks, is started by WP-Cron. When WP-Cron has been stalled, that queue falls behind too, so check it again once WP-Cron is running.

A fix we made

On one site we look after, scheduled tasks stopped for three days before anyone noticed. WP-Cron was switched off in wp-config.php and the host had no cron job set up. A plugin had been starting WP-Cron as a side effect, and when it was removed in a plugin clean-up, nothing scheduled ran. One of the stalled tasks was the caching plugin’s clean-up of old pages, so visitors who were not logged in were served out-of-date pages with expired security tokens, and multi-step forms failed for them only.

We added a small runner on the server side that starts WP-Cron at most once a minute, which fixed the forms. A cron job in the hosting control panel is the long-term replacement. Since then, before switching any plugin off we check whether DISABLE_WP_CRON is set, and after changes we check for overdue events and test forms while logged out.

When to get help

Stop if scheduled posts and backups still do not run after a server cron job is in place, if the host does not offer cron jobs and Site Health reports loopback failures you cannot clear, or if you are not comfortable editing wp-config.php. A shop that relies on scheduled tasks for orders, emails or subscriptions is a reason to get help sooner.

What a developer would check

  • Whether DISABLE_WP_CRON is set and a server cron job or other runner replaces it.
  • Loopback requests to wp-cron.php through firewalls, security plugins and the content delivery network.
  • Overdue events in WP Crontrol, and which plugins own them.
  • Action Scheduler queues for WooCommerce and subscription plugins.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Does WP-Cron run if nobody visits my site?
No. It is only started by a page load. On a quiet site, tasks wait for the next visit. A server cron job removes that dependence, because the server runs it on a timetable.
Is it safe to turn WP-Cron off?
Only with something to replace it. DISABLE_WP_CRON stops visits from starting WP-Cron, so a server cron job has to call it. WordPress notes that its cron system uses very little server power, so replacing it is not required unless you need tasks to run on time.
How often should the server cron job run?
WordPress’s example uses every 15 minutes. For scheduled posts that must go out close to their time, a shorter gap, such as every 5 minutes, keeps them closer to it. WP-CLI’s --due-now option avoids two runs overlapping.

Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on WordPress 7.1.