Lorixen.
EN

Scheduled posts and tasks that never run in WordPress

Short answer: WordPress doesn't have a clock running in the background. Its scheduler, WP-Cron, only checks for due tasks when someone loads a page. On a quiet site, or one where caching or security settings stop that check from firing, scheduled posts show "Missed schedule" and plugin tasks like backups and reminder emails run late or not at all. The reliable fix is to have your server's real scheduler call wp-cron.php every few minutes and switch off the page-load trigger.

You scheduled a blog post for 7 a.m. Monday, and at noon it still says "Missed schedule". Or your booking plugin's reminder emails go out hours late, or the nightly backup ran at lunchtime. These look like separate problems, but they usually share one cause. This guide goes from symptom to cause to fix.

How WP-Cron actually works

WordPress's Plugin Handbook explains it directly: WP-Cron checks, on every page load, a list of scheduled tasks and runs any that are due during that page load. It doesn't run constantly like the system cron on a server does. The handbook's own example: schedule a task for 2:00 p.m., and if no page loads happen until 5:00 p.m., that's when it runs.

The same page explains the trade-off. WP-Cron exists because many shared hosts don't offer access to the system scheduler. Unlike a system cron job that simply doesn't retry if its time passes, WP-Cron queues tasks and runs them at the next opportunity, so you can't be sure when a task runs, but it will run eventually. Core features such as publishing scheduled posts and checking for updates rely on it, and so do many plugins.

Symptom 1: "Missed schedule" on posts

Likely cause: no visit triggered WP-Cron near the scheduled time, or the trigger fired but failed.

On a low-traffic business blog, early-morning posts are the classic victim: nobody visits at 7 a.m., so nothing checks the queue.

Fix: set up a real cron job (see the fix section below). As a quick test, load any page of your site; if the post publishes shortly afterwards, the trigger was the problem.

Symptom 2: Plugin emails, reminders or reports arrive late

Likely cause: same mechanism. Booking reminders, abandoned-cart emails, newsletter queues and report generators often use WP-Cron. If traffic is uneven, timing is uneven.

Fix: real cron. If a task needs precise timing (a reminder 24 hours before an appointment), page-load triggering is simply not suitable.

Symptom 3: Nothing scheduled runs at all

Likely causes:

  • DISABLE_WP_CRON was set to true in wp-config.php (perhaps by a previous developer or host) but no real cron job replaced it.
  • The server can't make the internal HTTP request WP-Cron uses to spawn itself, often due to security rules, basic-auth protection on a staging site or firewall settings.
  • A full-page cache serves visitors without WordPress running, so page loads never reach the scheduler.

How to check: if you or your host can use WP-CLI, the wp cron test command tests the spawning system. According to its documentation it checks whether DISABLE_WP_CRON is set (and errors if so, because WP-Cron is disabled), warns if ALTERNATE_WP_CRON is set, and attempts to spawn WP-Cron over HTTP. wp cron event list lists scheduled events, so you can see which tasks are overdue.

Symptom 4: The site slows down at random moments

Likely cause: heavy scheduled tasks (imports, large emails, backups) running during a visitor's page load.

Fix: move WP-Cron to a real scheduler so tasks run in the background rather than on a visitor's request.

The fix: hand scheduling to the server

WordPress's handbook describes the solution in two parts.

1. Set up a system task to call wp-cron.php. Use your server's scheduler to make a web request to wp-cron.php at the interval you need. On Linux and macOS that's cron, typically edited with crontab -e; on Windows, the Task Scheduler. Most hosting control panels offer a "Cron jobs" screen that does the same without a terminal. A common setup is every five or fifteen minutes; the handbook shows the cron syntax for a fifteen-minute interval. Ask your host which command format they recommend; some prefer a PHP command, others a web request.

2. Turn off the page-load trigger. Once the server calls WP-Cron on schedule, WordPress no longer needs to check on every page load; the handbook notes this adds unnecessary resource use. Add this line to wp-config.php:

define( 'DISABLE_WP_CRON', true );

Do these in order. Disabling the page-load trigger before the system task works is exactly how sites end up in Symptom 3.

After the fix: check it worked

  1. Schedule a test post for ten minutes ahead and confirm it publishes on time.
  2. If you have WP-CLI, run wp cron event list and check that no events are long overdue.
  3. Watch the plugin tasks that were late, such as reminders and backups, over the next few days.
  4. Note the cron job in your site documentation, so a future host move doesn't silently drop it.

A note on managed hosting

Some managed WordPress hosts already run WP-Cron from the server and set DISABLE_WP_CRON for you. Others leave it to page loads. Check your host's documentation or ask support before adding a second scheduler, because running both is harmless but wasteful, and a missing one is the real problem.

FAQ

Is "Missed schedule" a sign my site was hacked?

Almost never. It means the scheduler didn't fire at the scheduled time. Real cron is the usual fix.

How often should the cron job run?

It depends on your most time-sensitive task. Every five to fifteen minutes suits most business sites. Very frequent calls on a busy shared host add load for little benefit.

Will real cron help my backups and emails too?

Yes. Any plugin that schedules tasks through WP-Cron benefits, because tasks run on time instead of waiting for a visitor.

Can I fix it without server access?

If your host offers a cron job screen in its control panel, you can set it up there. If not, ask the host; external services that ping a URL on schedule are another option.

When scheduled posts and reminders keep slipping and you're not sure what your host runs, tell us where the site is hosted and we'll help you set up scheduling that keeps time.

Sources

WhatsAppLet’s talk