Sébastien Laframboise

Monitor WordPress cron jobs with a suitable tool

Monitor WordPress cron jobs with a suitable tool

A scheduled post that’s late, a backup that won’t start, or a plugin that appears inactive can have the same cause: WordPress cron tasks didn’t run when expected. Before randomly changing settings, check the scheduled events, their timing, and their status.

An inspection tool like WP Crontrol makes this check accessible from the admin. That way you can tell the difference between a simple delay and a task that’s missing, duplicated, or tied to a plugin needing your attention.

Why a scheduled task can be late

WP-Cron is the mechanism WordPress uses to handle deferred actions. The core uses it for some update checks and for scheduled posts. Plugins and themes can also register their own recurring tasks with it.

However, WP-Cron doesn’t work like a standalone server scheduler. WordPress checks for due events when a page load triggers the process. As a result, a low-traffic site can run a task after its expected time. The official WP-Cron documentation explains this dependency on visits.

A slight delay therefore doesn’t automatically mean a task is faulty. However, multiple overdue events, repeated warnings, or duplicate tasks warrant a methodical check.

Install WP Crontrol to view events

To inspect events without the command line or file edits, install WP Crontrol from the official WordPress directory. The plugin displays scheduled tasks, their arguments, recurrence, associated action, and next run time.

After activation, open Tools > Cron Events. Each row represents an event created by WordPress, a theme, or a plugin. Always start by observing the list before changing anything.

Avoid deleting, modifying, or pausing a task whose origin you don’t know. An automation may support a backup, a sync, an email send, or order processing.

Information to review

  • The event hook: its name helps identify the component that created the task.
  • Next run: an overdue time indicates an event is still awaiting its trigger or encountering an obstacle.
  • Recurrence: it specifies whether the task repeats at regular intervals or is intended to run only once.
  • Arguments: they can distinguish two events that share the same name.
  • Warnings: they can reveal a missed schedule or an issue with the cron system.

Note the exact name of the suspicious task, its schedule and the plugin that appears to have created it. Then check that plugin’s settings and documentation. This precaution prevents jumping to conclusions based on an event’s name alone.

How to check a delayed scheduled task

First identify events whose next run time has passed. Then see whether the same hook appears multiple times with similar times or arguments. Repetition can indicate that a component registered multiple tasks for the same action.

Plugins that create recurring tasks should check whether an equivalent event already exists. Otherwise, multiple schedules can accumulate. The official reference on scheduling a recurring event describes the role of recurrence and arguments in identifying events.

Also examine tasks that no longer appear linked to any usable action. They may come from a deleted or deactivated plugin. Still, confirm their origin before deleting anything. A core task, or a task recreated automatically, should not be treated as mere residue.

Re-run an event without creating a duplicate

WP Crontrol lets you request immediate execution of an event. This option helps verify whether the action can start under current conditions. For example, you can re-run a backup task, then check the tool’s log and the intended location for the created file.

Before re-running a task, make sure it won’t trigger duplicate processing. Be especially careful with commands, renewals, synchronizations and batch sends. After a backup, follow the steps to verify that a WordPress backup is complete and recent.

A successful manual run doesn’t guarantee future schedules. It shows instead that the action can work now. Monitor the next occurrence to confirm that behavior returns to normal.

Recognize a general triggering problem

When several unrelated tasks are delayed, the issue may affect triggering in general rather than a single plugin. Low traffic can explain the delay. In addition, security restrictions, internal request errors or limited server resources can prevent the process from starting.

In that case, check WP Crontrol warnings, logs provided by your host and messages from the relevant plugin. If the admin area is slow too, start by find the cause of a slow WordPress dashboard. A heavy or overly frequent task can contribute to the slowdown without being the sole cause.

For a site that relies on one-off actions, such as frequent backups or commercial automations, ask your host whether they offer a server-side scheduler. This solution reduces dependence on visits. The host should, however, adapt it to your environment, and you should confirm that events do run.

Add this check to site maintenance

Monitoring WordPress cron tasks integrates easily into regular maintenance. Check the list after adding a major plugin, after a migration and when an automation no longer produces the expected result.

A monthly check is often enough for a simple editorial site. Conversely, a site that handles orders, subscriptions or frequent backups requires closer monitoring. Add this check to your monthly WordPress maintenance.

Finally, keep a short note of tasks you re-ran, deleted or paused. That way you can more easily link a change to abnormal behavior and provide precise information to the host or developer if needed.