Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Developer · Guide

How to View WP Cron Events (Step by Step)

How to View WP Cron Events (Step by Step)

Short answer

WordPress has no built-in screen for cron events, so install the free WP Crontrol plugin and open Tools > Cron Events to see every hook, its next run and recurrence. Developers can run wp cron event list with WP-CLI, or call _get_cron_array() in PHP to read the same schedule.

Key takeaways

  • WP Crontrol adds a Cron Events screen under Tools with run, edit and delete actions.
  • WP-CLI lists events with wp cron event list and can export them to CSV.
  • Events are stored as one serialized option named cron, so avoid editing it by hand.
  • WooCommerce jobs live in Action Scheduler under Tools > Scheduled Actions.
  • Overdue events usually mean WP Cron is not firing, not that the task is broken.

How do you view WP Cron events?

Install the free WP Crontrol plugin and open Tools > Cron Events, or run wp cron event list with WP-CLI, to see every scheduled event, its hook, next run time and recurrence.

WordPress has no built-in screen for cron events. The schedule is stored in the database, and you need a plugin, WP-CLI or a little PHP to read it.

Here is how the main methods compare:

MethodBest forNeeds
WP Crontrol pluginMost site ownersAdmin access
Advanced Cron Manager pluginAn alternative dashboard viewAdmin access
WP-CLIDevelopers and hosts with SSHCommand line access
PHP functionsCustom checks in codeA code snippet or plugin
Database lookupRead-only inspectionphpMyAdmin or similar

If you want to know how WP Cron works first, read our guide on whether WP Cron runs automatically.

What is a WP Cron event?

A WP Cron event is a task that WordPress or a plugin schedules to run a hook at a set time, either once or on a repeating schedule such as hourly or daily.

Each event has a few parts:

  • Hook: the action name that runs, such as wp_version_check
  • Arguments: optional data passed to the callback
  • Next run: the timestamp when it should fire next
  • Recurrence: the schedule name, such as hourly, twicedaily, daily or weekly, or none for single events
  • Callback: the PHP function attached to the hook

WordPress core schedules its own events for update checks, deleting old auto-drafts and other housekeeping. Plugins add more for backups, emails, imports and cleanups.

The Cron chapter of the Plugin Handbook explains how events are scheduled and why they only run when the site gets a visit.

How do you view cron events with WP Crontrol?

Install and activate WP Crontrol, then go to Tools > Cron Events to see a table of all scheduled events with their hook, arguments, next run and recurrence.

Step by step:

  1. Go to Plugins > Add New Plugin
  2. Search for WP Crontrol
  3. Click Install Now, then Activate
  4. Open Tools > Cron Events
  5. Use the search box or filters to find a hook
  6. Hover over a row to see actions such as Run now, Edit and Delete

WP Crontrol is maintained by John Blackbourn and is widely used for this job. It also flags events that have missed their schedule, which helps when something is stuck.

The plugin shows the callback functions attached to each hook. If an event has no callback, it will run but do nothing, which often points to a plugin that was removed without cleaning up.

What does each column in the cron events list mean?

The list shows the hook name, any arguments, when the event runs next, how often it repeats, and which functions run when it fires.

Reading the columns:

ColumnWhat it tells you
HookThe action name the event triggers
ArgumentsData passed to the callback, often empty
Next RunDate and time of the next run, plus how long until then
ActionThe callback function or functions attached
RecurrenceThe schedule, or Non-repeating for one-off events

Times show in your site's time zone. If a next run time is in the past, the event is overdue. A few minutes late is normal on low-traffic sites, because WP Cron waits for a page load.

Events that are hours or days overdue usually mean cron is not firing at all. Our guide to fixing WP Cron not running covers the usual causes.

How do you see cron schedules and intervals?

In WP Crontrol, open Settings > Cron Schedules to see every recurrence name and its interval in seconds, including custom schedules that plugins add.

Core WordPress includes hourly, twicedaily, daily and weekly. Plugins often add their own, such as every five minutes or every fifteen minutes.

WP Crontrol lets you add custom schedules from this screen. Most site owners never need to, but it is useful when testing a plugin that expects a schedule that no longer exists.

With WP-CLI, the same list appears with the command below:

wp cron schedule list

How do you view cron events with WP-CLI?

Connect to your server over SSH, go to the WordPress folder, and run wp cron event list to print every scheduled event in a table.

The basic command:

wp cron event list

You can choose the columns you want. This shows the hook, the relative time until the next run and the recurrence:

wp cron event list --fields=hook,next_run_relative,recurrence

You can also filter by hook or export the list:

wp cron event list --hook=wp_version_check
wp cron event list --format=csv > cron-events.csv

The wp cron event list reference lists every field and format. Many managed hosts include WP-CLI, so check your host's SSH docs if you are not sure.

How do you run or test a cron event from WP-CLI?

Use wp cron event run with a hook name to run that event now, use the due-now flag to run everything overdue, and use wp cron test to check that cron can spawn.

Useful commands:

wp cron event run wp_version_check
wp cron event run --due-now
wp cron test

Running an event manually is a safe way to check whether the callback works. If the task works when you run it by hand but never on its own, the problem is the cron trigger, not the code.

The wp cron test command checks whether WordPress can make the loopback request it uses to start cron. A failure here often points to a firewall, basic authentication or a host block.

How do you view cron events with PHP?

Call _get_cron_array() to get the full schedule as an array keyed by timestamp, or wp_next_scheduled() to get the next run time for one hook.

A quick check for a single hook:

$next = wp_next_scheduled( 'my_plugin_daily_task' );
if ( $next ) {
    echo 'Next run: ' . wp_date( 'Y-m-d H:i:s', $next );
} else {
    echo 'Not scheduled';
}

To inspect everything, loop over the array:

foreach ( _get_cron_array() as $timestamp => $hooks ) {
    foreach ( $hooks as $hook => $events ) {
        error_log( $hook . ' at ' . gmdate( 'c', $timestamp ) );
    }
}

The leading underscore in _get_cron_array() marks it as a private function. It is fine for debugging, but plugins should use the public functions such as wp_next_scheduled() and wp_get_scheduled_event().

The output goes to the debug log in the second example. Our guide on reading the WordPress debug log shows where to find it.

Where are WP Cron events stored in the database?

WP Cron events are stored as one serialized value in the options table, in the row where option_name is cron.

You can see it in phpMyAdmin by searching the options table (wp_options with the default prefix) for that row. The value is a long serialized PHP array, which is hard to read by eye.

Treat this as read only. Editing serialized data by hand can break the whole array, and WordPress may then lose every scheduled event. Use WP Crontrol or WP-CLI to change events instead.

Some object cache setups keep options in memory. If you change cron data at the database level, flush the object cache so WordPress sees the change.

How are WooCommerce scheduled actions different from WP Cron events?

WooCommerce and many other plugins use Action Scheduler, which stores its jobs in its own tables and shows them under Tools > Scheduled Actions, not in the WP Cron list.

Action Scheduler still uses WP Cron to start its queue runner. So in WP Crontrol you will see a single action_scheduler_run_queue event, while the individual jobs live in a separate list.

To view them:

  1. Go to Tools > Scheduled Actions (WooCommerce also links to it from WooCommerce > Status)
  2. Filter by Pending, Complete, Failed or Past-due
  3. Search by hook or group

Our explainer on what Action Scheduler is covers how it works, and the Action Scheduler documentation has the developer details.

If you see a long list of past-due actions, read fixing past-due actions in WooCommerce.

What should you look for when you review cron events?

Look for overdue events, duplicate hooks, events with no callback, and very frequent schedules from plugins you no longer use.

A short checklist:

  • Overdue events: next run times far in the past mean cron is not firing
  • Duplicates: the same hook listed many times can point to a plugin bug
  • Orphans: events with no action left behind by deleted plugins
  • Heavy schedules: tasks every minute can add server load on busy sites
  • Unknown hooks: search the hook name to find which plugin owns it

Delete orphaned events only when you are sure the plugin is gone for good. If the plugin is still active, it may add the event back on the next page load.

Should you switch to a real server cron?

Yes, if events often run late or your site gets little traffic, because a server cron job triggers WP Cron on a fixed timetable instead of waiting for visitors.

The setup has two parts. First you add DISABLE_WP_CRON to wp-config.php, then you create a server cron job that calls wp-cron.php or runs WP-CLI every few minutes.

Our step-by-step guide on disabling WP Cron and using a real cron job covers both parts. After the switch, check Tools > Cron Events again to confirm that next run times stay current.

Frequently asked questions

Does WordPress have a built-in cron viewer?

No. WordPress stores scheduled events but has no admin screen for them. You need a plugin such as WP Crontrol, the WP-CLI cron commands, or a short PHP snippet to see what is scheduled and when it runs next.

Is it safe to delete WP Cron events?

It is safe to delete events left behind by plugins you have removed. Do not delete core events like update checks, and remember that an active plugin will usually schedule its event again on the next page load.

Why are my cron events showing as late?

WP Cron only runs when someone loads a page, so quiet sites run events late. Long delays usually point to disabled cron, a blocked loopback request or a fatal error in a scheduled task. A real server cron job fixes most cases.

Where do I see WooCommerce scheduled tasks?

WooCommerce uses Action Scheduler, which keeps its jobs in separate tables. Open Tools > Scheduled Actions to see pending, completed, failed and past-due actions. The WP Cron list only shows the single event that starts the Action Scheduler queue.

Can I export a list of cron events?

Yes. With WP-CLI, run the cron event list command with the CSV format option and save the output to a file. This gives you every hook, next run time and recurrence in a spreadsheet-friendly format.

Sources

  1. WP Crontrol WordPress.org Plugin Directory
  2. Cron WordPress Plugin Handbook
  3. wp cron event list WordPress Developer Resources
  4. _get_cron_array() WordPress Code Reference
  5. Action Scheduler documentation Action Scheduler

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.