Troubleshooting · Troubleshooting
How to Fix "Missed Schedule" on Scheduled Posts in WordPress
Short answer
A “Missed Schedule” post passed its publish time because WP-Cron, the scheduler that publishes it, did not run when due. WP-Cron only checks for due tasks when a page loads, so quiet sites, caching, a blocked loopback request, or a switched-off WP-Cron can leave the post waiting. Publish the missed post by hand, then fix the trigger with a real server cron job so the next post goes out on time.
Key takeaways
- “Missed Schedule” means the post passed its publish time while still holding “future” status.
- WP-Cron only runs on page load, so a post due at 2:00 PM can wait until the first visit at 5:00 PM.
- Site Health under Tools flags late scheduled events and failed loopback requests.
- Set the server cron job up first, then add DISABLE_WP_CRON to wp-config.php, never the other way round.
- Kinsta runs a platform cron every 15 minutes, while WP Engine's Alternate Cron checks every minute.
What does “Missed Schedule” mean in WordPress?
“Missed Schedule” means a post passed its set publish time but stayed unpublished, so WordPress flags it in the posts list.
A scheduled post holds the “future” status until its publish event runs. WordPress keeps that status in the post record, and the list view adds the red “Missed Schedule” label when the date has passed.
The post itself is usually fine. The timer that should have published it did not run.
That timer is WP-Cron, the built-in scheduler. The Plugin Handbook Cron guide states that WP-Cron "does not run constantly as the system cron does; it is only triggered on page load."
Its example is a task set for 2:00 PM that runs at 5:00 PM, when the first visit arrives. A missed post is the same delay, stretched past the point where WordPress flags it.
Why do scheduled posts miss their time?
Most misses come from WP-Cron never running at the due time, not from a broken post.
Work through the causes in this order, most likely first:
- No visits at the due time. WP-Cron checks for due tasks only when a page loads, so a quiet night leaves the post waiting. DreamHost notes that scheduled posts are triggered by the first visit on or after the set time, as the DreamHost scheduling guide explains.
- Full-page caching. A cached page can be served without loading WordPress, so the visit never reaches WP-Cron. If cached pages are the suspect, see the guide on changes not showing on the live site.
- A blocked loopback request. WP-Cron starts by asking the site to call its own wp-cron.php file, and a firewall, security rule, or login wall can block that self-request. The loopback request fix guide covers that check.
- WP-Cron switched off with no replacement. If wp-config.php sets DISABLE_WP_CRON to true and no server job calls wp-cron.php, nothing scheduled runs at all.
- Wrong timezone. The post was set for the wrong hour because the site timezone did not match the time you meant.
Kinsta warns that disabling WP-Cron first, without a replacement job, makes scheduled tasks stop running silently, including post scheduling, backup jobs, plugin update checks, and email notifications.
Its guide to disabling WP-Cron also notes that wp-cron.php fires on every page load by default, which can add load on a busy site. If that load is a worry, read the guide on fixing high CPU usage.
How do you publish a missed post right now?
Open the post, fix the date if it is wrong, then click Publish to put it live at once.
- Go to Posts → All Posts and open the post marked “Missed Schedule”.
- Check the date and time in the Publish panel and fix any wrong hour.
- To go live now, click Publish. To try again later, pick a new future time and click Schedule.
- Visit the public post URL in a private browser window to confirm it loads.
If the same post misses again, do not keep rescheduling it. The cause sits in the scheduler, so work through the checks below before you set another time.
The Learn WordPress scheduling tutorial shows the same controls for pages, and notes that you click Schedule a second time to confirm. A scheduled post then appears in the dashboard with “Scheduled” next to it.
How do you check the timezone before you reschedule?
Open Settings → General, pick a city in your timezone, save, and check the local time shown on the page.
WordPress.org's Settings General screen docs say to choose a city in the same timezone as you. The docs give New York as the example for the US Eastern timezone that honors daylight saving time. That page was updated on 3 July 2026, as of November 2026.
After you click Save Changes, the page shows the UTC time and the local time so you can confirm the choice. A city entry follows daylight saving time changes. A fixed UTC offset does not, so it can shift your schedule by an hour twice a year.
Changing the timezone does not fix a post that already missed. It only sets the right clock for the next post you schedule, so publish the missed post by hand first.
How does Site Health show a WP-Cron problem?
Open Tools → Site Health → Status and read any warning about scheduled events or loopback requests.
Site Health can report “A scheduled event is late” or “A scheduled event has failed” as recommended improvements, and it names the hook that missed. A loopback warning means WordPress could not call its own site, so WP-Cron could not start. Both warnings point at the scheduler rather than the post.
Note the hook name, the time, and any error code before you change anything. That note tells your host exactly which task failed. If Site Health shows no warning, the miss may come from low traffic or caching rather than a broken request.
How do you test WP-Cron with WP-CLI?
Run wp cron test from the site folder and read the one-line result.
The wp cron test docs say the command checks whether DISABLE_WP_CRON is set, warns if ALTERNATE_WP_CRON is set, and tries to start WP-Cron over HTTP. A working setup answers “Success: WP-Cron spawning is working as expected.” A response other than HTTP 200 draws a warning.
Two more commands help. wp cron event list shows each scheduled event and its next run time. wp cron event run --due-now runs every event that is due right now, as the wp cron event docs describe.
If wp cron event run --due-now publishes the missed post but the site never does it alone, the trigger is the fault, not the post.
If the test reports an error while DISABLE_WP_CRON is set, that error is expected by design, so check the server job instead. If your host gives no shell access, skip this section and use Site Health plus the host checks below.
How do you replace WP-Cron with a real server cron job?
Add a server job that calls wp-cron.php every 5 to 15 minutes, confirm it runs, then set DISABLE_WP_CRON to true in wp-config.php.
Back up the site before you edit wp-config.php, as the WordPress backup guide describes. The handbook page on hooking WP-Cron into the system scheduler gives the order: set up the system task first, then stop the page-load trigger.
- In your hosting panel or server crontab, add a job that requests wp-cron.php. The handbook example uses
wget --delete-after http://YOUR_SITE_URL/wp-cron.phpwith your real site address. - Set the job to run every 15 minutes (
*/15 * * * *). Kinsta runs its own platform cron every 15 minutes, and it allows custom jobs no more often than every 5 minutes. - Wait for at least one run, then check that a test post publishes on time.
- Add
define( 'DISABLE_WP_CRON', true );to wp-config.php above the “That's all, stop editing!” line. - Schedule a test post 10 minutes out and leave the site alone until it passes.
| Interval | Cron timing | Best for |
|---|---|---|
| 5 minutes | */5 * * * * | Posts that must go out close to their time |
| 15 minutes | */15 * * * * | Most blogs; Kinsta runs its platform cron every 15 minutes |
| 30 minutes | */30 * * * * | Low-traffic sites where timing can slip by half an hour |
If your host supports WP-CLI, the job can run wp cron event run --due-now from the site folder instead of wget. That runs due events directly and skips the self-request. Either route needs the same order: job first, DISABLE_WP_CRON second.
What should you do if your host already runs a server cron?
Check your host's docs first, because many managed hosts already run a server cron and only need DISABLE_WP_CRON set.
| Host | Server trigger | How often | What you do |
|---|---|---|---|
| Kinsta | Platform server cron on every site | Every 15 minutes | Add DISABLE_WP_CRON to wp-config.php |
| WP Engine | Alternate Cron service | Every minute | Turn on the Alternate cron toggle under Utilities |
WP Engine's wp-cron support page says its Alternate Cron checks for due crons every minute by curling wp-cron.php. The toggle sets DISABLE_WP_CRON for you, and adding the line yourself does not enable Alternate Cron. It also does not work behind custom basic-auth protection, because the cron must reach the site in public.
If your host is not listed here, ask support one question: "Do you run a server cron for wp-cron.php, and what do I need to set?" Their answer decides whether you build the job yourself. If you are still choosing a host, the WordPress hosting requirements guide lists what a host should provide.
How do you know the fix worked?
Schedule a test post 10 minutes out, do not visit the site, and check the public URL after the time passes.
- The test post shows as Published, not “Missed Schedule”, in Posts → All Posts.
- Site Health → Status shows no new scheduled-event or loopback warning.
wp cron event listshows no event hours overdue, if you have WP-CLI.
Repeat the test once more at a quiet hour, such as early morning. One pass at midday does not prove the fix, because daytime visits may have masked the fault.
When should you contact your host?
Contact your host when Site Health reports a loopback failure you cannot trace, or when a server cron you set up never runs.
- The loopback test fails after you deactivate caching and security plugins one at a time.
- wp-cron.php returns a 404, a 403, or a timeout when you request it.
- You have no shell or cron panel access and need a server job created.
- Misses continue after a server cron is running and the timezone is right.
Send the host the hook name from Site Health, the post time, and the exact error. That detail lets support check the server log instead of guessing.
What mistakes should you avoid?
The costliest mistake is setting DISABLE_WP_CRON before the server job exists, which stops all scheduled tasks at once.
- Rescheduling the same post again and again without checking Site Health or the timezone.
- Picking a fixed UTC offset instead of a city, so daylight saving time shifts the publish hour.
- Installing several missed-schedule recovery plugins at once instead of fixing the trigger.
- Editing wp-config.php without a backup in place.
A recovery plugin can help as a safety net. The Missed Scheduled Posts Publisher plugin on WordPress.org checks for missed posts every 15 minutes and publishes them, with no settings page. Treat it as a net, not a fix: it publishes posts after they are already late.
Frequently asked questions
Can I just republish a missed post and forget about it?
Yes, for that one post. Open it, fix the date if it is wrong, and click Publish. The post goes live at once. But the next scheduled post can miss the same way, so check the timezone and Site Health, then set up a server cron job if misses keep happening.
Why do only some scheduled posts miss their time?
WP-Cron runs when a page loads, so timing depends on traffic. A post due at a busy hour may publish on time because a visit triggers it, while a post due overnight waits until the first morning visit. Caching and loopback blocks add to the pattern, so misses often look random when they are really tied to quiet hours.
Does a missed-schedule plugin fix the problem for good?
No. A recovery plugin publishes posts after they are already late, which is useful as a safety net but does not fix the trigger. The lasting fix is a real server cron job that calls wp-cron.php on a set interval, with DISABLE_WP_CRON set only after that job is running.
How often should the server cron job run?
Every 5 to 15 minutes suits most sites. Kinsta runs its platform cron every 15 minutes, and WP Engine's Alternate Cron checks every minute. A 15-minute job means a post can still go out up to 15 minutes late, so use 5 minutes when timing matters. Do not set a custom job more often than your host allows.
Will changing the timezone fix posts that already missed?
No. Changing the timezone only sets the right clock for posts you schedule next. A post that already missed stays unpublished until you publish it by hand or set a new future time. Check the timezone first, then fix the missed post, so the new time you pick is the one you mean.
What if my site has almost no traffic?
A server cron job matters most on a quiet site, because WP-Cron needs a page load to run. Set up a job that calls wp-cron.php every 15 minutes, confirm it runs, then set DISABLE_WP_CRON. Without visits or a server job, scheduled posts have no trigger at all.
Sources
- Scheduling WP Cron Events WordPress Developer Resources
- Hooking WP-Cron Into the System Task Scheduler WordPress Developer Resources
- Settings General Screen WordPress.org
- Disabling WP-Cron (wp-cron.php) for Faster Performance Kinsta
- Configure wp-cron and Event Scheduling WP Engine Support
- How to Schedule Posts on WordPress DreamHost
- Scheduling posts and pages Learn WordPress
- wp cron test WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
