Black FridayCyber Monday 2026
14Days
15Hrs
34Mins
42Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

“Missed Schedule” in WordPress: Fix Scheduled Posts That Do Not Publish

Scheduled posts rely on WP-Cron, which only runs when someone loads a page. Learn why posts get missed and how to make scheduling reliable.

wpallsolution 7 min read

A missed schedule in WordPress means that a post you scheduled for a certain time did not publish when it should have. In the posts list it is marked “Missed schedule”, and the post stays unpublished until something nudges it. This usually has nothing to do with the post itself. WordPress runs scheduled tasks with a mechanism called WP-Cron, and WP-Cron only runs when someone loads a page. This guide explains that, how to rescue the post, and how to make scheduling reliable.

Quick answer

If a post shows “Missed schedule”, open it and publish it now (or set a new time). To stop it happening again, find out why WP-Cron was late: the site may have little traffic, the loopback request may be failing, wp-cron.php may be blocked or cached, or WP-Cron may have been disabled with no replacement. The reliable fix is to run a real scheduled job on the server that calls WordPress every few minutes.

How this guide was prepared: it is research-based. We used the WordPress Plugin Handbook on cron and the WordPress source code listed under Sources, checked on October 23, 2026. We did not test your host, so check the cron options your hosting plan offers.

How WordPress schedules posts

When you schedule a post, WordPress gives it the status “future” and creates a scheduled event for its publish time. The handbook explains that WP-Cron is triggered on page load: it checks its list of tasks during a visit and runs any that are due. It does not run on its own clock. A task due at 2:00 PM waits until somebody loads a page, and missed tasks are queued and run at the next page load. WordPress also has a safeguard, check_and_publish_future_post, that the scheduled event calls so a future post is published only when it is really due.

If the event runs too late or never runs, the post is shown as “Missed schedule” in the posts list, a label defined in the WordPress admin code. The Site Health screen can also warn you, with messages such as “A scheduled event is late” or “A scheduled event has failed”, which the Site Health code says may indicate that scheduling posts or automated updates may not work as intended.

The decision tree: why did the post miss its time?

Flowchart for a missed schedule in WordPress: five questions about the stuck post, Site Health events, loopback, blocked wp-cron.php and low traffic
Five questions show why a scheduled post was missed.
  1. Post stuck as Missed schedule? Publish it now (Step 1).
  2. Site Health reports a late or failed event? Treat it as a WP-Cron problem (Step 2).
  3. Site Health reports a loopback failure? Fix that first (Step 3).
  4. wp-cron.php blocked, cached or password protected? Let it through (Step 4).
  5. Low traffic, or WP-Cron disabled? Use a real cron job (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Posts publish, but lateLow traffic, so WP-Cron only runs at the next visitStep 5
Posts never publish by themselvesWP-Cron disabled, blocked or failingSteps 2 to 5
Site Health shows “A scheduled event is late”Events are not being run on timeSteps 2 and 5
Site Health shows a failed loopback requestThe site cannot call itselfStep 3
Site behind a password or firewallThe scheduler request is refusedStep 4

5 steps to fix a missed schedule in WordPress

Step 1: Publish the post and note what was affected

Open the post and choose Publish (or set a new time). Check other scheduled posts, which may be late too. Take note of the time you scheduled and the time it should have published, because the gap tells you whether the problem is lateness (low traffic) or failure (blocked or disabled).

Step 2: Read what Site Health says about scheduled events

Open Tools → Site Health. Look for a scheduled event warning. Our guide to WordPress Site Health explains the screen. A late event suggests WP-Cron runs too rarely; a failed event suggests the request could not complete. If you see the message about DISABLE_WP_CRON, someone switched the default mechanism off, which is fine only if a real cron job replaces it.

Step 3: Fix a failing loopback request

WordPress documents that loopback requests are used to run scheduled events. If Site Health reports that your site could not complete a loopback request, a security plugin, firewall, basic authentication, a maintenance plugin or a hosting rule may be blocking the site from calling itself. Fix this first, otherwise scheduling will keep failing. Test by pausing the likely plugin on a staging copy; see how to find the plugin that broke your site.

Step 4: Make sure wp-cron.php can run

The scheduler request goes to wp-cron.php. If a page cache, a CDN rule, a firewall or a password prompt covers that file, the request fails or returns a cached copy. Exclude it from caching and from authentication, and check that the file exists and answers without an error.

Step 5: Run a real cron job

For a low traffic site, the dependable fix is a server task that calls WordPress on a schedule instead of waiting for a visitor. The handbook shows how: set define( 'DISABLE_WP_CRON', true ); in wp-config.php to stop the page load trigger, then create a system cron job that requests wp-cron.php, for example every few minutes with wget --delete-after https://yoursite.com/wp-cron.php (the handbook uses a daily example; for scheduled posts a short interval such as every 5 minutes is our suggestion). If you have WP-CLI, wp cron event run --due-now runs events that are due. Your host’s control panel usually has a “Cron jobs” screen. Do not disable WP-Cron without adding the job, or nothing will run.

Version and hosting differences

  • Some managed hosts run their own scheduler, so ask your host before you change wp-config.php.
  • Shared hosts may limit how often a cron job can run.
  • Caching and security plugins can interfere with the scheduler request, so recheck them after changes.

How to verify the fix

  • A test post scheduled a few minutes ahead publishes on time.
  • Site Health no longer reports late or failed scheduled events.
  • The cron job appears in your host’s log or runs when you test it.

How to prevent it from happening again

  • Use a real cron job on any site where timing matters, such as content calendars and stores.
  • Test scheduling after hosting, caching or security changes.
  • Check Site Health regularly; see what WordPress maintenance includes.

Frequently asked questions

What does “Missed schedule” mean?

The post’s publish time has passed, but WordPress did not publish it, usually because the scheduled event did not run on time.

Why does it happen on low traffic sites?

WP-Cron runs only when a page loads, so a quiet site may not trigger it on time.

Is it safe to disable WP-Cron?

Only if you replace it with a real cron job. Otherwise scheduled posts, updates and other tasks stop.

Will a plugin fix it?

A plugin that publishes missed posts can help as a safety net, but the dependable fix is a working scheduler.

What to do next

Publish the missed post, read Site Health and set up a real cron job. If you would rather not touch the server, wpallsolution offers WordPress maintenance packages and an emergency WordPress fix. We cannot promise results without seeing your hosting.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us