WordPress Cron Jobs Not Running? 11 Fixes That Actually Work

WordPress dashboard with a clock showing scheduled tasks that never run
Scheduled posts and tasks that never run are the classic sign of a broken WordPress cron system.

When wordpress cron jobs not running becomes your problem, the signs are easy to miss at first. A scheduled post stays unpublished past its time. A backup plugin never sends its report. An email that should go out at 9 in the morning never arrives. Your site looks fine on the surface, but nothing happens on schedule behind the scenes.

The good news is that this problem is almost always fixable. WordPress does not run tasks on a real clock. It runs them when somebody visits your site. That design works well on busy sites, but it fails on quiet sites, on sites behind a cache, and on sites where a plugin or a server setting blocks the background request. This guide explains the cause in plain words and walks you through eleven fixes in order, from the simplest check to testing the cron file directly. Follow them one by one and your scheduled tasks will run again.

If your whole site is down rather than just its scheduled tasks, read our guide on fixing a WordPress website that will not load first, because a site that cannot load cannot run any task at all.

Table of Contents

  • Why This Error Happens
  • Quick Checks
  • Diagnose: Match Your Symptom to the Cause
  • Fix 1: Visit Your Site to Trigger the Missing Tasks
  • Fix 2: Check Your Timezone and Scheduled Post Times
  • Fix 3: Check Whether a Caching Plugin Blocks Background Requests
  • Fix 4: Test With All Plugins Deactivated
  • Fix 5: Check Your Theme for a Broken Cron Hook
  • Fix 6: Install a Plugin That Shows Your Scheduled Tasks
  • Fix 7: Set Up a Real Server Cron Job
  • Fix 8: Check With Your Hosting Provider
  • Fix 9: Repair the Database Tables That Store Scheduled Tasks
  • Fix 10: Delete Stuck or Duplicate Scheduled Events
  • Fix 11: Visit the wp-cron.php File Directly in Your Browser
  • What to Avoid
  • Frequently Asked Questions
  • Conclusion

Why This Error Happens

1. WordPress Cron Only Runs When Someone Visits Your Site

WordPress uses a system called WP-Cron. It is not a real clock on the server. It is a list of tasks that WordPress checks each time a page loads. When wordpress cron jobs not running is the complaint, the most common cause is simply a quiet site. If nobody visits for hours, no page loads, and no task is checked. Scheduled posts then sit unpublished until the next visitor arrives. This is normal WordPress behaviour, not a bug, but it feels like a fault on a new or low-traffic site.

2. A Wrong Timezone Shifts Every Scheduled Task

WordPress stores scheduled times in UTC and shows them in your local timezone. If the timezone in Settings is wrong, a post you meant to publish at 9 in the morning may be set for 9 at night, or even for the next day. The task is not broken. It is simply waiting for a time that has not come yet. A wrong timezone also confuses plugins that send daily emails or run nightly clean-up jobs.

3. Caching Stops the Background Request From Reaching WordPress

Many caching plugins and hosts serve a saved copy of each page without loading WordPress at all. That is good for speed, but it means the WP-Cron check never happens on cached visits. Some security plugins and firewalls also block the background request that WordPress sends to itself. When that request is blocked, scheduled tasks pile up silently and nothing runs on time.

4. A Plugin or Theme Hook Breaks the Schedule

Plugins register their own scheduled tasks, and a single badly written one can break the whole list. A plugin that throws an error during its task can stop later tasks from running. A theme can do the same thing if it registers a task in its functions file and that code has an error. The problem often starts the day a new plugin is installed or an old one is updated.

5. Your Host Blocks the Loopback Request

WordPress triggers its own cron by sending a request back to itself, which developers call a loopback request. Some hosts block loopback requests for security, and some servers are set up so the site cannot reach itself by its own domain name. When the loopback fails, WordPress cannot start its tasks in the background, and every scheduled job waits forever.

6. The Scheduled Task List in the Database Is Damaged

All scheduled tasks live in a database option called the cron option. If that data is damaged by a failed update, a database error, or a plugin that writes bad data, WordPress cannot read the list at all. Tasks may still show in a plugin, or they may vanish completely. Either way, nothing runs until the stored list is repaired or rebuilt.

Quick Checks

  • Open your site in a browser and wait a few seconds, then check whether the missed task has run.
  • Look at your scheduled posts under Posts and check the exact date and time on each one.
  • Open Settings, then General, and confirm the timezone matches your real location.
  • Clear your site cache once, then visit the homepage again.
  • Check whether the problem started right after you installed or updated a plugin.
  • Look at your hosting dashboard for any error notice or failed task message.
  • Try a different browser or an incognito window to rule out a browser cache problem.

Diagnose: Match Your Symptom to the Cause

SymptomCauseGo to Fix
Scheduled posts publish late, only after you visit the siteLow traffic, so WP-Cron is never triggeredFix 1
Posts publish at the wrong hourWrong timezone in SettingsFix 2
Tasks stopped after you installed a caching pluginCache serves pages without loading WordPressFix 3
Tasks stopped after a new plugin or updateA plugin is breaking the scheduleFix 4
A feature added by your theme never runs on timeTheme code registers a broken taskFix 5
You cannot see which tasks exist or when they runNo tool is showing the scheduleFix 6
Tasks never run even on a busy siteBackground requests are blocked, so a real server cron is neededFix 7
Nothing in WordPress explains the failureHost blocks loopback requests or the server clock is wrongFix 8
Tasks are missing or the list looks corruptDamaged cron data in the databaseFix 9

Fix 1: Visit Your Site to Trigger the Missing Tasks

This is the simplest test, and it tells you a lot. WP-Cron runs when a page loads, so a visit can clear a whole backlog of missed tasks in seconds.

  • Open your homepage in a browser and let the page load fully.
  • Wait about thirty seconds, then open your dashboard.
  • Check your scheduled posts. If one has now published, the cron system works and your site simply needed a visitor.
  • Visit the site again a few times over the next hour and watch whether new tasks run on time.
  • If tasks only run when you visit, your site has too little traffic to trigger WP-Cron on its own, and Fix 7 will solve it for good.
  • Ask a friend in another country to visit the site too, so you can rule out a problem with your own browser or network.

This fix takes one minute and costs nothing. It also confirms the diagnosis before you change any setting. If visiting does not trigger anything at all, move on to the next fix.

A scheduled WordPress post still showing as a draft after its publish time
A scheduled post that stays unpublished past its time is the clearest sign that the cron system is stuck.

Fix 2: Check Your Timezone and Scheduled Post Times

A wrong timezone is one of the most common causes of this problem, and it takes two minutes to check.

  • In your dashboard, go to Settings, then General.
  • Look at the Timezone field and make sure it shows your real city or time zone.
  • Check the line underneath it, which shows the current local time according to WordPress. It should match the time on your computer or phone.
  • If the time is wrong, pick the correct timezone and save your changes.
  • Now open Posts, then All Posts, and look at your scheduled posts.
  • Click Quick Edit on a scheduled post and check its date and time carefully.
  • Fix any post that is set for the wrong hour, then update it.
  • Schedule a test post for five minutes from now and watch whether it publishes on time.

If the test post publishes at the right time, the problem was the timezone all along. If it still does not publish, the schedule itself is broken and the next fixes will help.

Fix 3: Check Whether a Caching Plugin Blocks Background Requests

Caching is good for speed, but it can stop WP-Cron from running. Cached pages are served without loading WordPress, so the cron check never happens.

  • Open your caching plugin settings and look for an option about caching the homepage or logged-out visitors.
  • Purge or clear the whole cache once, then visit your homepage.
  • Check whether your missed tasks have now run.
  • Look for a setting that excludes the file wp-cron.php from caching, and turn it on if you find one.
  • If your host has its own server cache, open the hosting dashboard and purge that cache too.
  • Ask your host whether their cache blocks the wp-cron.php request, and ask them to allow it.
  • Test again with a scheduled post set five minutes ahead.

Do not delete your caching plugin in a hurry. Most caching tools work fine with WordPress cron once the background request is allowed through. The official WordPress developer guide on cron explains how the system is meant to work, and it is worth reading before you change server settings: WordPress developer guide to WP-Cron.

Fix 4: Test With All Plugins Deactivated

A single plugin can break the whole schedule. This test finds it fast, and it is safe if you follow the steps in order.

  • Before you start, write down which plugins are active, or take a screenshot of the Plugins page.
  • Go to Plugins, then Installed Plugins, and deactivate every plugin.
  • Schedule a test post for five minutes from now and watch whether it publishes.
  • If the test post publishes, one of your plugins is the cause.
  • Reactivate your plugins one by one, testing a scheduled task after each one.
  • When the problem comes back, the last plugin you turned on is the culprit.
  • Keep that plugin deactivated and contact its developer, or find a replacement that does the same job.
  • If deactivating all plugins does not help, reactivate them all and move to the next fix.

This method is the same one used to find a WordPress plugin conflict, and it works because it removes every suspect at once and then adds them back one at a time.

WordPress plugins list where a conflicting plugin can be deactivated
Deactivating plugins one by one quickly shows whether a plugin is blocking scheduled tasks.

Fix 5: Check Your Theme for a Broken Cron Hook

Themes can register scheduled tasks too, and a theme error can stop the schedule from running.

  • Switch to a default WordPress theme such as Twenty Twenty-Four for a short test.
  • Go to Appearance, then Themes, and activate the default theme.
  • Schedule a test post for five minutes from now and watch whether it publishes.
  • If the test post publishes with the default theme, your theme is part of the problem.
  • Switch back to your own theme and check whether it was recently updated.
  • Look in the theme settings for any scheduled feature, such as a daily import or a rotating banner, and turn it off for the test.
  • Contact the theme developer and tell them the exact time the problem started and which task fails.
  • Do not edit the theme files yourself unless you know PHP well, because a small mistake can break the whole site.

If the default theme does not fix the problem either, your theme is innocent and the cause lies somewhere else.

Fix 6: Install a Plugin That Shows Your Scheduled Tasks

You cannot fix what you cannot see. A cron viewer plugin shows every scheduled task, when it should run next, and whether it is late.

  • In your dashboard, go to Plugins, then Add New, and search for a well-rated cron viewer plugin from WordPress.org.
  • Install it and activate it, then open its page in the Tools menu.
  • Look at the list of tasks and check the next run time on each one.
  • Any task marked as late or overdue is a clue. Note its name and the plugin that registered it.
  • Try running one overdue task by hand from the plugin, if it offers that option.
  • If a task fails when you run it by hand, the plugin that owns it is likely broken.
  • Delete tasks that belong to plugins you no longer use, but only after you are sure they are safe to remove.
  • Keep the viewer plugin installed for a few days so you can watch whether tasks start running on time.

A viewer plugin changes nothing on its own, but it turns a mystery into a list you can work through. It also helps your host support team, because you can tell them exactly which task is late.

WordPress timezone setting in Settings General that affects when cron jobs run
A wrong timezone makes scheduled tasks run at the wrong time — or look like they never ran.

Fix 7: Set Up a Real Server Cron Job

This is the permanent fix for most sites. A real server cron job calls WordPress on a fixed schedule, so tasks run even when nobody visits.

  • First, add one line to your wp-config.php file to stop WordPress from running its own cron on page loads. The line is define(‘DISABLE_WP_CRON’, true); and it goes above the line that says “That is all, stop editing”.
  • Be careful with this file. Download a copy first, and edit it with a plain text editor, not a word processor.
  • Next, open your hosting control panel and find the Cron Jobs section.
  • Add a new cron job that runs every five minutes.
  • The command should call the wp-cron.php file on your site with a tool like wget or curl. Your host support team can give you the exact command for their servers, and the usual form calls your own site address followed by /wp-cron.php?doing_wp_cron, with output sent to nowhere.
  • Save the cron job and wait for the next run.
  • Schedule a test post for ten minutes from now and watch whether it publishes on time.
  • Check your cron viewer plugin after an hour. Tasks should now show recent run times instead of overdue ones.

This fix removes the traffic problem completely. Your tasks now run on the server clock, not on visitor traffic. If your host does not offer cron jobs, ask their support team what they offer instead, because most good hosts do.

Server cron job settings in a web hosting control panel
A real server cron job can trigger WordPress tasks on a fixed schedule, even without visitors.

Fix 8: Check With Your Hosting Provider

If nothing in WordPress explains the failure, the server itself may be blocking the background request.

  • Contact your host support team and tell them that wordpress cron jobs not running is the problem on your site.
  • Ask them to check whether loopback requests to your own domain are blocked.
  • Ask them to check the server time and the server timezone, because a wrong server clock shifts every task.
  • Ask whether their firewall or security rules block the wp-cron.php file.
  • Ask them to check the server error log for the time a scheduled task should have run.
  • If they find a block, ask them to allow requests to wp-cron.php from the server itself.
  • While you wait, test your site from a different network, such as your phone data, to rule out a problem with your own internet connection.

Hosts deal with this problem often, so they usually know the answer in minutes. If your host cannot fix it and cannot explain it, that is useful information too. A host that blocks basic WordPress features is a poor home for a WordPress site.

Fix 9: Repair the Database Tables That Store Scheduled Tasks

This is the last resort, and it fixes a damaged task list in the database. Take a full backup before you start, and stop if any step feels unclear.

  • Make a full backup of your site, including the database, and download it to your computer.
  • Open your hosting control panel and find the database tool, which is often phpMyAdmin.
  • Open your WordPress database and find the options table, which is usually called wp_options.
  • Search for the row with the option name cron and check whether it exists.
  • If the row is missing, WordPress will rebuild it, but your old tasks will be gone and plugins will register theirs again.
  • If the row exists but looks damaged, delete only that one row, then visit your site so WordPress rebuilds the list.
  • Check your cron viewer plugin to see whether tasks have returned.
  • If the problem is still there after a rebuild, ask your host to repair the database tables from their side.

Never delete other rows in the options table. That table holds your site address, your admin email, and many other settings. Deleting the wrong row can take your whole site down, which is why the backup matters so much. If a WordPress critical error appears after any database change, restore the backup at once and ask your host for help.

Fix 10: Delete Stuck or Duplicate Scheduled Events

A stuck or duplicated event can clog the whole schedule. When a plugin registers the same task twice, or when a task fails halfway and never clears, WordPress keeps trying the broken copy and the healthy tasks wait behind it. Clearing the bad copies gives the schedule a clean start.

  • Open your cron viewer plugin from Fix 6 and look for tasks marked overdue by hours or days.
  • Look for the same task name listed twice, or a task with no next run time at all.
  • Delete only the duplicate or stuck copy, and keep the one with a proper next run time.
  • If a task belongs to a plugin you deleted long ago, delete that task too, because nothing will ever run it.
  • Visit your homepage once, then check the viewer again to see whether the list looks clean.
  • Schedule a test post for ten minutes from now and watch whether it publishes on time.

Do not delete tasks that belong to plugins you still use. Those tasks will come back on their own the next time the plugin runs, and deleting them only hides the problem for a day. Delete only duplicates, stuck copies, and tasks left behind by deleted plugins.

Fix 11: Visit the wp-cron.php File Directly in Your Browser

Calling the cron file yourself is a quick test. It shows whether the file runs at all when something asks for it directly, instead of waiting for a visitor or a background request.

  • Click into your browser address bar and type your site address followed by /wp-cron.php?doing_wp_cron at the end.
  • Press Enter and wait a few seconds for the page to load.
  • A blank page is normal. It means the file ran without an error.
  • Now check your dashboard or your cron viewer plugin to see whether any overdue tasks have run.
  • If tasks have now run, the cron file works when called directly, and the problem is the background request that should call it for you.
  • If the browser shows an error page or times out, write down the exact message. That message tells your host exactly what is failing.
  • If the direct visit works but scheduled tasks still fail on their own, the server cron job from Fix 7 is the answer, because it calls this same file on a fixed schedule.

This test takes one minute and costs nothing. It separates a broken cron file from a broken background request, and that difference decides which fix you need next.

What to Avoid

  • Do not install a random cron plugin from an unknown site. Only use plugins from WordPress.org or a vendor you trust.
  • Do not edit wp-config.php without a backup copy saved on your computer first.
  • Do not delete database rows unless you know exactly which row you are deleting.
  • Do not set a server cron job to run every minute. Every five minutes is enough for most sites and puts less load on the server.
  • Do not assume the task is broken when it may only be late. Check the timezone before you change anything else.
  • Do not keep requesting the same scheduled task over and over. Duplicate tasks can pile up and make the problem worse.
  • Do not use a nulled plugin or theme from an unofficial download site. These often contain hidden code that breaks scheduled tasks and puts your site at risk.
  • Do not ignore the problem for weeks. Missed backups and missed emails can cost you data and customers.

Frequently Asked Questions

Why do my scheduled posts publish late instead of on time?

Scheduled posts publish late when nobody visits your site at the publish time. WordPress checks its task list only when a page loads, so a quiet site can miss the exact minute. A real server cron job fixes this for good, because it calls WordPress every five minutes whether visitors arrive or not.

How do I know whether WP-Cron is working at all?

Install a cron viewer plugin and look at the next run times. If tasks show recent run times, the system works. If every task is overdue by hours, the system is stuck. You can also schedule a test post five minutes ahead and watch whether it publishes without you visiting the site first.

Can a caching plugin really stop scheduled tasks?

Yes, it can. A cached page is served without loading WordPress, so the cron check never runs on that visit. Most caching plugins have a setting to exclude wp-cron.php, and turning that on solves the problem. Purging the cache and testing again will tell you quickly whether the cache is the cause.

Is it safe to disable WP-Cron and use a server cron job instead?

Yes, it is safe when you follow the steps in Fix 7. Disabling WP-Cron only stops WordPress from checking tasks on page loads. The server cron job takes over that job on a fixed schedule. Many large sites run this way because it is more reliable. Keep a backup of wp-config.php before you edit it.

What should I do if a task is overdue by days?

First check whether the plugin that owns the task is still installed and active. Then try running the task by hand from a cron viewer plugin. If it fails, deactivate that plugin and contact its developer. If many tasks are overdue at once, work through Fixes 3, 4 and 7 in order, because a cache, a plugin, or a missing server cron is the usual cause.

Does low traffic really cause this problem?

Yes. WordPress cron is triggered by visits, not by a clock. A site with only a few visitors a day can miss scheduled times by hours. This is the most common cause on new sites. A server cron job is the proper fix, and it works even on a site with no visitors at all.

Conclusion

When wordpress cron jobs not running is the problem, the cause is usually simple. Your site is quiet, your timezone is wrong, a cache is blocking the background request, or a plugin has broken the schedule. Start with the quick checks and the timezone, then test your plugins and your cache. If those do not fix it, set up a real server cron job so your tasks run on the server clock instead of waiting for visitors.

Work through the eleven fixes in order and test after each one. Do not change five things at once, because then you will never know which change fixed it. Once your scheduled posts publish on time and your daily tasks run as expected, keep your cron viewer plugin installed for a week and check it now and then. A healthy schedule is quiet and boring, and that is exactly how it should be.

If your site was stuck in maintenance mode during your testing, our guide on fixing WordPress stuck in maintenance mode will help you clear that too. For the official background on how WordPress schedules tasks, see the WordPress troubleshooting FAQ.

Leave a Reply

Your email address will not be published. Required fields are marked *