Blog / WordPress /

Why scheduled posts fail on WordPress (and WP-Cron)

You scheduled the post for 9am. It’s 9:15 and it’s still sitting there, smugly, as a draft. The editor is asking where it is. Where is it?

Usually the culprit is WP-Cron. Scheduled posts depend on WordPress’s pseudo-cron, which is triggered by site visits rather than running constantly like a server cron job. A quiet site, a wrong setting or something blocking the request can all stop it.

I start with the post’s scheduled time and the site’s timezone, then look at WP-Cron and any caching or security layers in the way. For a busy or business-critical publishing workflow, a real server cron can be more reliable, but set it up carefully with the host or developer.

How WP-Cron works

WP-Cron checks for scheduled tasks when someone visits the site. It is not a persistent background process that wakes up at an exact minute regardless of traffic. On a low-traffic site, a scheduled event may run later than expected because no request triggered the check.

Other issues can block the event: a timezone mismatch, a plugin conflict, a site migration, a fatal error or a configuration that disables WP-Cron without setting up a real cron job. A cache or firewall may also affect requests, though you should confirm this rather than guessing.

Scheduled publishing relies on the same mechanism. WordPress may show a “missed schedule” notice when the event did not run as expected. The post itself may be fine; the task that publishes it did not execute on time.

Check the simple causes first

Open the post and confirm it is scheduled rather than saved as a draft. Check the displayed date, time and timezone under WordPress settings. If the site recently moved, the server timezone or WordPress timezone may have changed. Compare the schedule with the timezone the editor expects.

Check whether the site has a DISABLE_WP_CRON setting in wp-config.php. Disabling WP-Cron can be appropriate when a server cron replaces it, but if no real cron is configured, scheduled tasks may stop running. I wouldn’t add or remove the constant without understanding the hosting setup.

Review plugin and theme updates around the time the problem began. A backup, security, caching or performance plugin may affect scheduled requests. Check error logs and the scheduled events list with a trusted tool or WP-CLI if available. Don’t run unfamiliar commands on production without a backup.

Restore missed posts safely

If a post missed its schedule, publish it manually after confirming the content and intended date. Check whether automated emails, feeds or social integrations will fire on manual publication. Avoid changing the publication time just to make the post appear at the top if that would misrepresent its date.

Test with a future-dated draft on staging where possible. Check that it publishes and that any connected integrations behave as expected. If the site has a content calendar, notify the people who expected the article to go live and agree on the new time.

Use a real cron when appropriate

A server cron can call WordPress’s cron endpoint on a schedule, reducing dependence on visitor traffic. The exact command and interval depend on the host and configuration. A hosting provider may offer a cron interface or recommend a method. Ask them to confirm the correct setup and whether the site’s existing WP-Cron should be disabled.

Don’t schedule the real cron more often than you need to. Repeated requests can add load, while a long interval may delay tasks. Consider other scheduled jobs such as plugin maintenance, backups and email queues. Document the owner and monitor the job after configuration.

A real cron is not automatically better for every site. A simple low-traffic site may work adequately with standard WP-Cron, while an active publishing or commerce site may benefit from a dependable server schedule. Choose based on the site’s tasks and operational requirements.

WP-Cron runs more than post publication. Plugins may use it for backups, updates, email queues, cache clearing or other tasks. If scheduled posts have failed, review whether other events are delayed too. A larger cron issue could affect maintenance or customer-facing processes.

After resolving the cause, monitor upcoming events and record the change. If the issue returns, use the logs and event list to identify whether the task was scheduled, triggered and completed. This is more useful than repeatedly rescheduling the same post.

Check the common causes in order

If a post misses its scheduled time, note the timezone shown in WordPress and compare it with the intended publishing time. A site can have a timezone setting that differs from the server’s, and daylight-saving changes can confuse a schedule if the team assumes a fixed offset. Confirm that the post is actually scheduled rather than saved as a draft, and check whether another editor changed its status.

Next review Site Health for a missed schedule event and inspect whether a caching, security or maintenance layer is blocking requests that trigger WP-Cron. Plugin conflicts are possible, but disabling plugins on a live site can create a second incident; use staging or coordinate a safe test. If the host provides cron jobs, ask how it recommends invoking WordPress scheduled tasks and whether the existing pseudo-cron trigger should be disabled. A real cron can make execution more predictable, but an incorrect command or duplicate schedules can cause trouble too. Test with a low-risk task, document the setup and make sure the site owner knows who maintains it.

Check the site’s timezone and whether a real cron is configured before you reschedule the next missed post. What other scheduled tasks on your site might depend on WP-Cron?