Choose a language

Small web team working together at a desk with a website on screen

WordPress Cron Jobs: Fix Missed Schedules

Published November 5, 2026 · 15 min read

WP-Cron is WordPress's built-in task scheduler, and it does not run on a clock. Every time a page on your site is loaded, WordPress quietly checks a list of scheduled tasks and runs whatever is due at that moment. That single design choice explains almost every "my scheduled post published late" or "my backup never ran" complaint.

In this guide you will see what actually happens on a page load, how to list and manage what is scheduled, when to disable WP-Cron and replace it with a real system cron job, and how to debug a task that keeps failing. No PHP expertise required beyond one short snippet.

The path in 6 steps

The steps of this page, in order.

  1. 01 See the trigger Understand that tasks run on page loads, not on a clock.
  2. 02 Find what's scheduled List the events waiting in your cron queue.
  3. 03 Check your traffic Decide whether site visits are frequent enough to be reliable.
  4. 04 Switch to real cron Disable WP-Cron and point a system scheduler at wp-cron.php.
  5. 05 Verify it works Confirm tasks now run on time and nothing runs twice.
  6. 06 Debug failures Fix missed runs, duplicates, and timezone mistakes.

01 / 09

What is WP-Cron, in plain English?

WP-Cron is WordPress's own scheduler, and unlike a server's cron it has no clock of its own: it waits for a page to be loaded and then runs whatever is overdue.

WP-Cron is WordPress's built-in task scheduler. Instead of checking the clock on a fixed timer, it waits until someone loads a page on your site, then looks for any tasks that are due. If no one visits for hours, those tasks wait too.

System cron (the Unix/Linux scheduler) works differently: it runs commands at exact times, whether or not a visitor is on the site. WordPress uses WP-Cron as a fallback because many shared hosts don't give site owners easy access to the server's scheduler.

Site administrator working on a laptop in a home office

Going further

Open the database view

02 / 09

Why do my scheduled tasks run late?

Because WP-Cron checks the queue on page loads, a task due at 2:00 PM may not run until 5:00 PM if nobody visits your site in between.

Every time a visitor loads a page, WordPress opens wp-cron.php, the file that reads the list of pending tasks from your database and runs the ones whose timestamp has passed. A scheduled event is one task in that queue, stored in the options table with a timestamp for when it should run. If no one visits, nothing runs.

So a task due at 2:00 PM can wait until 5:00 PM, or until the next morning on a quiet site. The upside: a missed task is not lost. It stays in the queue and fires at the next opportunity, unlike a system cron job that is simply skipped if its moment passes.

  1. A visitor requests a page

    Any front-end or admin page load triggers the check, not just scheduled posts.

  2. WordPress opens wp-cron.php

    The file connects to the database and reads the list of scheduled events stored in the options table.

  3. It compares timestamps

    Each event has a timestamp for when it should run. WordPress checks which ones are already due.

  4. Due tasks execute

    Tasks whose time has passed run in that request. Tasks not yet due are left alone.

  5. Missed tasks wait

    If no page load happens, nothing runs. The event stays queued and fires on the next visit.

Developer checking server data on two monitors

Going further

What about DDoS risk?

03 / 09

How do I see what is actually scheduled?

Two tools cover almost every case: the WP Crontrol plugin for a visual list, and WP-CLI for a command-line list when you have shell access.

WP Crontrol adds a screen under Tools where you can see every event, its next run time, its schedule, and the hook it is attached to. A hook is a named point in WordPress where your code attaches a function so it runs at a specific moment. You can also run an event immediately or delete it.

With WP-CLI, a command-line tool for managing WordPress without a browser, one command lists all events and another runs a specific hook on demand. That is faster when you are debugging on a server. Whichever tool you use, note the difference between the schedule name (hourly, daily) and the exact timestamp of the next run.

Plugin screen vs. command line

RouteAccess neededWhat you can doBest use case
WP CrontrolWP admin loginList events, check next run, run or delete an eventEveryday checks and quick fixes without shell access
WP-CLIShell or SSH accessList all events, run a specific hook on demandDebugging on a server, scripting, bulk checks

Both routes show the event list; the differences are where you stand and what you can change from there.

04 / 09

Which cron setup fits my site?

The right choice depends on two things only: how much traffic your site gets, and how much control your host gives you over the server.

Low-traffic sites are the worst case for WP-Cron, because long gaps between visits are exactly what delays tasks. If your host manages cron at the platform level, the page-load trigger already happens outside your site and you may not need to change anything.

The comparison below is the decision shortcut: match your situation to a row, and take the recommendation.

05 / 09

How do I replace WP-Cron with a real cron job?

Disable the page-load trigger, then point a real system cron job at wp-cron.php so it runs on a fixed schedule whether or not anyone visits.

First, add define('DISABLE_WP_CRON', true); to wp-config.php. That stops WordPress from firing its queue on visitor page loads, but the event list stays intact. Then create a real cron entry on the server that calls wp-cron.php every five or fifteen minutes. Traffic no longer decides when your tasks run.

Keep the schedule in one place so you can see it. A custom event is registered on a hook once, then unscheduled when you no longer need it, no orphaned jobs left running.

  1. Set DISABLE_WP_CRON to true

    Add define('DISABLE_WP_CRON', true); to wp-config.php above the 'That's all, stop editing' line. Check: save the file and reload any page, the scheduled list should still show your events, but none should fire from the page load itself.

  2. Create the system cron job

    In your host's cron panel or via crontab -e, add a command that requests wp-cron.php. A typical entry uses wget or curl to hit https://example.com/wp-cron.php. Check: run the command manually once and confirm it returns without a 404.

  3. Match the interval to the job

    Set the cron entry to every five or fifteen minutes, not every minute unless a task truly needs it. Check: wait one interval and confirm the next scheduled timestamp for a known event moves forward on its own.

  4. Verify traffic no longer matters

    Visit the site in a private window, then check the scheduled list again. Check: the event times should advance on the clock, not on how many visitors you sent.

Going further

Show the code

06 / 09

What does this cost, and is it worth it?

For most sites the cash cost is zero; the real cost is one small config change plus a few minutes of verification, against the risk of backups and posts that never fire.

Setting up a real cron job is free, since your hosting plan already includes the server's scheduler. Paid options, like external cron services or scheduling plugins, vary in price; treat any figure as a rough estimate and check the vendor's current pricing page.

The hidden cost is doing nothing: a missed backup, a post published hours late, or a failed renewal email. That risk grows with traffic and the number of scheduled tasks.

Worked example

Setup time vs. exposure to missed tasks

Configuration change
1 hour
Verification over one month
30 minutes
Assumed value of one missed critical task
$200
  1. Total setup time1.5 hours

    1 + 0.5

    Includes disabling WP-Cron and adding a system cron job.

  2. Break-even point0.0075

    1.5 ÷ 200

    You recover the time cost if you prevent one missed task worth $200.

  3. Annual savings if one task is missed per month$2,400

    200 × 12

    Hypothetical value; adjust to your own business.

What this result assumes
  • The $200 value per missed task is an explicit assumption, not a measured figure.
  • Time estimates assume you are comfortable editing a file or using a plugin.
  • External cron service prices are not included and vary by provider.

07 / 09

What can go wrong, and how do I fix it?

Almost every cron problem falls into three buckets: tasks that never run, tasks that run twice, and tasks that run at the wrong hour because of a timezone mismatch.

Match the symptom to the cause before editing anything. A task that never runs usually points to no traffic hitting the site, a system cron job that stopped executing, or a queue that was never cleared. A task that runs twice almost always means WP-Cron and a server cron are both active and firing the same event. Times off by whole hours point to a mismatch between the site's timezone setting and the server clock.

One warning applies to every site: wp-cron.php can be requested directly from the web, so a flood of requests can overload a server. The trade-off is the opposite risk, checking the queue on every page load costs performance on busy sites.

Missed schedules

Check the last run time first. Low-traffic sites may never trigger WP-Cron; a system cron job may have stopped.

Duplicate runs

Confirm only one trigger is active. If a server cron and WP-Cron both fire, the same task runs from two directions.

Timezone shifts

Compare the site timezone with the server clock. A mismatch moves every scheduled time by hours.

Wp-cron.php exposure

Block or throttle direct requests to that file, and weigh the cost of running the queue on every page load.

08 / 09

So what should I do first?

Check your traffic pattern first: if your site gets steady visits, WP-Cron is probably fine, and if it does not, switch to a real cron job today.

Start with your traffic pattern, not with a plugin or a service. If your site gets steady visits through the day, WP-Cron is probably firing on time and there is little to fix. If you see long overnight gaps, or fewer than a few visits an hour, move to a real cron job or your host's cron service today.

Leave a busy site alone and check the queue now and then. Bring in a developer only for custom scheduled tasks with error handling, or when your host will not give you shell access.

09 / 09

Frequently asked questions

Frequently asked questions
The Web Insider editorial team
About the author The Web Insider editorial team

Web Insider is a practical magazine for people who build, run or grow a website. Every fact is checked against its official source, and every test shows its proof.

Your feedback

Was this page helpful?

Share

Could this page help someone?

Related reading

Read next

Two colleagues reviewing a website admin screen on a large monitor
Websites & Platforms

WordPress Admin: How to Log In and Manage Your Site Safely

The WordPress admin lives at yourdomain.com/wp-admin on self-hosted sites, and behind the WordPress.com dashboard on hosted ones. Here is how to log in safely, find your way around, and recover access when something breaks.

·16 min
Analyst reviewing tag routing on a large wall screen
Websites & Platforms

GTM on WordPress: Install It Without Skewing Data

A non-commercial walkthrough to get your GTM container live on WordPress in under 30 minutes. The real work is data integrity: one method, no duplicate tags, verified before publish.

·16 min
Desktop monitor showing a structured content editing screen
Websites & Platforms

ACF for WordPress: What It Does and When to Use It

Advanced Custom Fields (ACF) is a free WordPress plugin by WP Engine that lets you attach extra structured content to posts, pages, and more. Here's what it does, when it's worth installing, and when it isn't.

·14 min
Two colleagues arranging blank planning cards on a dark wall board
Websites & Platforms

How to Organize a WordPress Site So It Stays Easy to Run

A practical system for solo owners and small teams who need their WordPress site to stay manageable as it grows. Pages vs posts, taxonomy, media, roles, and maintenance routines.

·16 min
E-commerce team checking store tracking on a laptop
Websites & Platforms

Google Tag Manager on PrestaShop: What to Check

GTM on PrestaShop only works when the container loads everywhere and a data layer feeds it real order values. Here is the order to check things so you find what is broken.

·17 min
Explore the topicData & Analytics

Audience measurement, Google Analytics 4 and Google Tag Manager: set them up, check them and keep your data reliable.

Explore the topicWebsites & Platforms

WordPress, Shopify, PrestaShop and WooCommerce: run, integrate and maintain a site without making it fragile.

Explore the topicGuides & How-Tos

Methods, training and practical benchmarks to scope a web project, test a site and make better decisions.

Explore the topicSecurity & Compliance

Backups, updates, GDPR, cookies and audience measurement: keep a site safe and compliant.