WordPress Missed Schedule: Why Scheduled Posts Don't Publish, and How to Fix It
"Missed schedule" in red next to a post means its publish time has passed and it's still waiting. WordPress has no clock running in the background: it checks for due tasks when someone visits the site. Here is why that fails, how to publish the stuck post now, and how to make scheduling reliable.
In this article
Key takeaways
- "Missed schedule" means the publish time passed before WP-Cron ran.
- WP-Cron runs only when someone loads a page and the site can call its own wp-cron.php.
- Publish the stuck post with Quick Edit, then fix the cause.
- Site Health flags failed scheduled events and blocked loopback requests.
- DISABLE_WP_CRON without a server cron stops every scheduled task.
- A server cron calling WP-Cron every 5 minutes makes scheduling reliable.
The short answer
Publish the stuck post by hand, then fix WP-Cron, the scheduler WordPress uses, which only runs when someone loads a page and the site can send a request to itself. In order:
- Publish the post now: Posts → Quick Edit → Status: Published.
- Check Tools → Site Health for “A scheduled event has failed” or “Your site could not complete a loopback request”.
- Make sure
wp-config.phpdoesn’t switch WP-Cron off with nothing to replace it. - For reliable timing, have the server run WP-Cron every 5 minutes and stop page loads from triggering it.
- Can’t add a server cron? A plugin or an outside service can fill in.
How WordPress publishes a scheduled post
- When you schedule a post, WordPress saves it as Scheduled and adds a one-off task,
publish_future_post, due at the post’s time. - At the end of each page load, WordPress checks its list of tasks. If one is due, it sends a quick background request from the site to its own
wp-cron.php, called a loopback request, and carries on serving the page. wp-cron.phpruns the task, which publishes the post if it’s still scheduled and its time has passed.
WordPress’s documentation puts the catch plainly: WP-Cron “does not run constantly as the system cron does; it is only triggered on page load.” A post scheduled for 2:00 PM on a site with no visits until 5:00 PM goes out at 5:00 PM. If the background request can’t get through, it doesn’t go out at all.
Once the time has passed, the posts list shows Missed schedule in red where it would say Scheduled.
Why it misses
| Cause | Why the post doesn’t go out | Fix |
|---|---|---|
| Few visits around the scheduled time | Nothing loads a page, so nothing starts WP-Cron | Server cron (step 4) |
| Full-page caching or a CDN | Cached pages are served without running WordPress, so those visits can’t start WP-Cron | Server cron (step 4) |
| The loopback request is blocked | A firewall, security plugin, password protection on the whole site, or a DNS or SSL problem on the server stops the site calling itself | Site Health (step 2), your host, or WP-CLI cron (step 4) |
DISABLE_WP_CRON without a server cron | WP-Cron is switched off and nothing replaces it | Step 3 |
| A plugin’s task fails | A fatal error in one scheduled task can stop the rest of that run | Find it in the debug log or WP Crontrol (step 5) |
1. Publish the stuck post now
- Go to Posts and find the post marked Missed schedule.
- Hover over it, click Quick Edit, set Status to Published and click Update. Or open the post and click Publish.
- The post keeps its scheduled date. If you want it to appear as your newest post, change the date to now first.
With WP-CLI, wp cron event run --due-now runs every task that’s due, including overdue publishing, and wp post list --post_status=future lists what’s still scheduled.
2. Check Site Health
Open Tools → Site Health. Two results matter:
- “A scheduled event has failed” or “A scheduled event is late”. WordPress flags a task as failed when it’s more than 5 minutes overdue, or more than an hour if you’ve moved WP-Cron to a server cron, and names the task.
- “Your site could not complete a loopback request”. WP-Cron can’t start, and the result includes the error. Send it to your host: a firewall, a security plugin or password protection on the whole site is the usual cause.
With WP-CLI, wp cron test runs the same check: it reports whether WP-Cron is switched off and whether WordPress can start it over HTTP. The WP-CLI cron docs list the other commands.
3. Check wp-config.php for DISABLE_WP_CRON
Open wp-config.php and look for this line:
define( 'DISABLE_WP_CRON', true );With it, page loads never start WP-Cron. That’s the right setup when a server cron runs it instead (step 4), and some managed hosts set that up for you. Without a server cron, nothing scheduled runs at all: posts, update checks or plugin tasks. Ask your host whether a server cron exists. If it doesn’t, add one or remove the line.
You may also see ALTERNATE_WP_CRON suggested. The wp-config.php documentation describes it as an option for when scheduled posts don’t publish: it redirects the visitor’s browser to run cron. The same page warns it “has certain risks”, so try the steps above first.
4. Run WP-Cron from a server cron
This is the fix WordPress’s own guide gives when tasks must run on time: have the server’s scheduler call WP-Cron every few minutes, then stop page loads from doing it. In your hosting panel (in cPanel, Cron Jobs) or with crontab -e, add one of these:
# Every 5 minutes, over HTTP:
*/5 * * * * wget --delete-after https://example.com/wp-cron.php
# Or every 5 minutes with WP-CLI, which also works behind a firewall or a site password:
*/5 * * * * cd /path/to/wordpress && wp cron event run --due-nowThen add this line to wp-config.php, above /* That's all, stop editing! */:
define( 'DISABLE_WP_CRON', true );Every 5 minutes is plenty for publishing: a post scheduled for 9:00 goes out by 9:05, with or without visitors. Check a day later that Site Health shows no failed events.
5. If you can't add a server cron
- See what’s stuck. WP Crontrol (300,000+ active installs, updated 15 October 2026, tested with WordPress 7.1.4) lists every scheduled task with when it’s due, runs one on demand, and warns about missed ones. It’s also the quickest way to spot a plugin task that keeps failing.
- Call WP-Cron from outside. Any service that requests
https://yoursite.com/wp-cron.phpevery few minutes, such as a scheduled check in an uptime monitor, does the same job as a server cron. - Patch the symptom. MWW Scheduled Post Trigger (60,000+ active installs, updated 13 September 2026) checks for missed scheduled posts when a visitor loads a page and publishes them. That fixes the posts, not WP-Cron, so other scheduled tasks can still run late.
- Mind the cache. If a page cache or CDN serves almost every visit, it can starve WP-Cron of page loads. Our guide to speeding up WordPress explains how caching works on WordPress.
Published at the wrong time instead?
If posts go out, but hours early or late, the cause is the site’s time zone rather than WP-Cron. Open Settings → General → Timezone and pick a city, such as London or New York, rather than a fixed UTC offset, so WordPress follows daylight saving time. Scheduled times are always read in the site’s time zone, not your computer’s.
Where WPOS fits
WPOS doesn’t replace WP-Cron; what it adds is the checking. WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own render with a browser screenshot before it reports a change as done. A Monday check of scheduled posts becomes one request:
“Find every post marked Missed schedule, publish them with today’s date, list any other scheduled tasks that are overdue, and take a screenshot of the blog page when you’re done.”
WPOS is our product, so weigh this section accordingly; you can try it free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card.
Frequently Asked Questions
The post's scheduled time has passed but WordPress hasn't published it. WordPress publishes scheduled posts with WP-Cron, which only runs when someone loads a page and the site can send a request to itself, so a quiet or heavily cached site can miss the time.
In Posts, use Quick Edit on the post and set its status to Published, or open it and click Publish. It keeps its scheduled date, so set the date to now first if you want it to appear as your newest post.
Usually one of these: too few visits around the scheduled time, a page cache that answers visitors without running WordPress, a firewall or password protection that blocks the site's request to itself, or WP-Cron switched off in wp-config.php with no server cron to replace it.
Have the server call wp-cron.php every few minutes with a cron job, then set the DISABLE_WP_CRON constant to true in wp-config.php so page loads stop triggering it. Posts then go out within a few minutes of their time, with or without visitors.
Only if something else runs it. WordPress uses WP-Cron for scheduled posts, update checks and plugin tasks, so turning it off without a server cron stops all of them.
Yes. When a page cache or CDN answers a visit, WordPress doesn't run, so that visit can't start WP-Cron. On a busy site some requests still reach WordPress, but on a quiet, fully cached site a server cron is the reliable fix.
Start free with 15,000 credits.
Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.
Catch stuck posts before your readers do.
WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own work. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.