A WordPress article was scheduled for the morning but appeared only when somebody visited the site later. Another task, such as a catalogue import, remains overdue. These observations may share a scheduling cause, but they are not proof that the hosting server was unavailable. Separate the moment a task became due, the moment it was triggered and the moment its work actually finished.
09:00: the task becomes due
In this illustrative timeline, an editor chooses 09:00 in WordPress. First check what that means: the site's timezone, the editor's intended timezone and the timestamp recorded by the task must agree. A display in UTC compared with a local calendar can create an apparent delay without any scheduler fault. Record the intended publication time with its timezone before changing settings.
WordPress explains that its normal WP-Cron mechanism checks scheduled tasks on page loads rather than running continuously. A quiet website can therefore reach a due time without immediately starting the task. This is a mechanism to investigate, not a universal explanation for every overdue event. Your installation may already have a separate system scheduler.
09:20: somebody visits the site
The visit and publication now appear close together. Ask whether WP-Cron was triggered successfully and whether the event ran once. Look at the existing task information and relevant logs through authorised read-only access. A page that loads successfully does not establish that a background request completed. Likewise, a failed background request does not prove that every public page is broken.
A task can start and then fail inside a plugin. It may wait on an external service, hit an application error or overlap with an earlier run. Record the hook or task name, its owner and the last known completion. Do not respond by clicking a “run all” control: scheduled tasks can send messages, modify orders or perform other real actions.
10:00: the investigation chooses a branch
- No trigger reached the due task
Check the current scheduler arrangement and the site's ability to invoke the required handler. Establish whether access rules, credentials or an incorrect path are involved before asking for changes.
- The trigger arrived, but execution failed
Give the plugin or application owner the narrow error window. A more frequent schedule will not repair a repeatable application exception.
- Work completed, but the result looked old
Compare the saved publication state with the rendered page and its cache. A stale display and a missing execution are different incidents.
Keep the evidence small: timestamps, task name, outcome and a redacted error description. Avoid sharing cookies, tokens, full customer records or an entire production log. This makes the issue easier to reproduce and reduces unrelated noise for the person responsible.
Before replacing the scheduler
A system scheduler can invoke WordPress on an agreed cadence. The official integration guide describes that arrangement. However, disabling the default trigger before a replacement is installed and verified can leave no working trigger at all. Confirm who owns the scheduler, which user executes it, what timezone it follows and how failures are noticed.
Test the proposed arrangement in an isolated environment with a harmless task. Keep mail, billing, external integrations and real customer data disconnected there. Validate one due event, repeated invocations and a failed attempt before applying an authorised production change. Preserve a usable rollback to the last verified arrangement; do not improvise two competing schedulers and assume they are harmless.
Our guide to workers and scheduled jobs on a VPS explains the broader ownership question. For WordPress, also review what specialised hosting should include. A WordPress hosting enquiry is more useful when it states which jobs matter, how late they may be and who maintains their plugins.
The acceptance test is simple to describe: a harmless scheduled task becomes due, starts within the agreed window, completes once and leaves evidence of that completion. Publishing one article successfully does not validate payment, email or import tasks with different dependencies.
Sources: WordPress WP-Cron overview and system scheduler integration.



