WP-CRON TIMINGScheduled posts on timeA post set to publish at 9:00 is still sitting in the Posts list at 10:30, marked "Missed schedule". A sale price starts late, or a plugin's daily email turns up in the afternoon. Usually nothing is broken. WordPress's scheduler, WP-Cron, runs when people visit the site, not when the clock says so, and the fix is a small server change.
Why do WordPress scheduled tasks run late?
Because WP-Cron only runs when a page loads. On each page load, WordPress checks its list of scheduled tasks and starts any that are due, using a background request from the server to wp-cron.php. The handbook's example: a task set for 2:00 PM with no page loads until 5:00 PM runs at 5:00 PM. Nothing is lost, because overdue tasks wait for the next opportunity, but nothing is on time either.
Three situations make the gap worse:
- Quiet sites. Overnight, at weekends or on a B2B site outside office hours, there may be no visits near the scheduled time. WooCommerce's own documentation warns that low traffic can delay scheduled tasks.
- Heavily cached sites. Caching plugins serve pages as static files, and WordPress's documentation describes
wp-config.phpas loading for every page view not served from a cache file. A visit answered from the cache skips the normal WordPress page load, so it never checks the schedule. - Failed loopback requests. Scheduled events run through a request from the site to itself. When that fails, Site Health reports that the site could not complete a loopback request, and tasks stall even with plenty of visitors.
What depends on WP-Cron?
More than most teams expect. Site Health describes scheduled events as what checks for core, plugin and theme updates and what makes sure scheduled posts are published on time. Plugins use the same system for their own jobs:
- Scheduled posts. Each one gets its own single event,
publish_future_post, set for its publish time. - Plugin jobs, from scheduled emails to cleanups.
- WooCommerce. WP-Cron handles scheduled sale prices and starts Action Scheduler, the queue behind order notifications, payment processing and webhooks.
On a store, check the Scheduled Actions screen too; we covered it in our WooCommerce database guide.
Isn't a busy site safe?
For timing, mostly. For server load, not quite: every page view still checks the schedule. WordPress spawns a run at most once a minute by default, controlled by WP_CRON_LOCK_TIMEOUT, and since WordPress 6.9 it spawns at the end of the request, so it no longer delays the first byte of the page. Even so, the handbook says that once a system scheduler calls wp-cron.php, the page-load check is no longer necessary and adds extra resource usage.
How do you put WP-Cron on a real clock?
Schedule a real job first, then switch off the page-load check. Keep that order: once DISABLE_WP_CRON is set, nothing runs scheduled events except your job.
- Create the job. On a server with crontab, run due events with WP-CLI, or request
wp-cron.phpover HTTP if WP-CLI isn't installed. On Windows servers, Task Scheduler can call the same URL with PowerShell. Many shared hosts don't give direct access to the system scheduler, so look for a cron jobs screen in the hosting panel. - Add the
DISABLE_WP_CRONline towp-config.php. - Check the next day that nothing is overdue, using the tools below.
// wp-config.php
define( 'DISABLE_WP_CRON', true );
# crontab, every 5 minutes, with WP-CLI
*/5 * * * * wp cron event run --due-now --path=/path/to/wordpress --quiet
# or the same over HTTP
*/5 * * * * wget --delete-after https://example.com/wp-cron.phpWe prefer the WP-CLI route where SSH is available. It runs on the server instead of through a web request, and --due-now respects the same lock WordPress uses, so two runs don't overlap. In the HTTP version, --delete-after stops wget saving a copy of every response.
Pick the interval from your tightest deadline. The handbook's examples run every 15 minutes or once a day. We usually start at five minutes, and go to every minute only when something must land exactly on time.
How do you see what is scheduled?
Start with WP-CLI, then cross-check in the dashboard:
wp cron event listshows each hook with its next run time and recurrence.wp cron event run --due-nowruns everything due, which is handy for testing the new job.wp cron testchecks the page-load spawner. OnceDISABLE_WP_CRONis set it reports an error by design, so don't read that as a fault.- Tools > Site Health flags "A scheduled event is late" or "A scheduled event has failed" and names the hook. With
DISABLE_WP_CRONon, it allows more slack: late after 15 minutes overdue, failed after an hour. - Without SSH, the free WP Crontrol plugin lists and runs events from the dashboard.
In the list, look for three things: events overdue by hours, meaning nothing is triggering cron; hooks from plugins you removed, because WordPress keeps trying to run tasks a plugin never unscheduled; and one hook scheduled many times, which happens when code schedules an event on every page load without checking first.
Where to start
Open the Posts list and Tools > Site Health. A "Missed schedule" label or a late scheduled event means it is time to move WP-Cron onto a real schedule, so check whether your host gives you cron access. Our WordPress development service covers this setup and a check of what is already queued, or get in touch to talk it through.
FAQ
Frequently asked questions
Is it safe to set DISABLE_WP_CRON to true?
Yes, as long as a real scheduler runs WordPress's due events. The constant only stops the check on page loads: scheduled events stay queued and run when your cron job calls wp-cron.php or WP-CLI. Add the constant without a job, though, and scheduled posts, update checks and other WP-Cron tasks stop running until someone notices.
What does ALTERNATE_WP_CRON do?
It makes WP-Cron use a redirect. When tasks are due, the visitor's browser is sent back to the page with a doing_wp_cron parameter, and the tasks run in the connection it dropped. WordPress's docs say it is mostly used when scheduled posts aren't publishing, and that it has certain risks. It still needs visits, and wp cron test warns when it is on.
Why does a scheduled post say Missed schedule?
WordPress shows that label in the Posts list when a post's publish time has passed but it is still marked as scheduled. The post goes live when its publish_future_post event finally runs, which on a quiet site may be the next visit. If it stays stuck for hours, check Site Health and look for that hook in the event list.
What happens to tasks that were missed?
They run on the next cron run, once each. A recurring task is then rescheduled for its next slot after the current time, so a daily cleanup that missed three days runs once, not three times. Single events, such as a scheduled post or a one-off email, simply run late.
Does WooCommerce need anything extra?
Usually nothing beyond the real cron job. WooCommerce's background work, such as order notifications, payment processing and webhooks, runs through Action Scheduler, which WP-Cron starts by default, so a fixed schedule helps the store's queue too. For large queues, Action Scheduler's docs recommend running it with WP-CLI, using wp action-scheduler run, instead of the default runner.
Do we need SSH or WP-CLI to fix this?
No. A cron job that requests wp-cron.php over HTTP works without WP-CLI, and if your host has a cron jobs screen in its panel you can add it there without SSH. WP-CLI is still worth having: it lists, runs and tests scheduled events from the command line, which makes problems much quicker to diagnose.

