WP-Cron Event Registry
Lists every scheduled WP-Cron event with its hook name, next scheduled run timestamp, how overdue it is (if applicable), and its recurrence interval. Events are sorted chronologically so overdue items surface immediately.
Full visibility into WP-Cron events and Action Scheduler jobs — so you know what's running, what's failing, and what's overdue.
WordPress background tasks run silently. WP-Cron jobs fire on page load without any dashboard visibility. Action Scheduler queues can build up thousands of failed or stuck jobs without triggering any alerts. The Cron Inspector surfaces the complete state of both systems — giving you the data you need to diagnose timing issues, identify failed background tasks, and understand exactly what scheduled work your WordPress site is performing.
Lists every scheduled WP-Cron event with its hook name, next scheduled run timestamp, how overdue it is (if applicable), and its recurrence interval. Events are sorted chronologically so overdue items surface immediately.
Any WP-Cron event whose next run timestamp is in the past is flagged as overdue. On WordPress sites where WP-Cron is disabled or infrequently triggered, overdue background tasks can accumulate undetected — this check makes the backlog visible.
If your site uses Action Scheduler (installed by WooCommerce, GravityForms, and many other plugins), the module displays pending, running, failed, and completed job counts separately. A large failed count signals a queue pipeline problem.
All WP-Cron events are displayed in a unified, time-sorted table so you can see the order in which WordPress background tasks are scheduled to execute and identify any clustering that might cause performance spikes.
Every cron event is displayed with its hook name, making it easy to trace which WordPress plugin registered a given scheduled task and what it does when it fires.
No. The Cron Inspector reads the _cron option from the WordPress options table and the Action Scheduler tables using SELECT queries only. It cannot schedule, cancel, or modify any event.
An overdue event is one whose scheduled timestamp is in the past but has not yet fired. On low-traffic sites where WP-Cron relies on page loads to trigger, events can fall significantly behind their intended schedule.
Plugins like WooCommerce and GravityForms use Action Scheduler heavily. High "Completed" counts are often normal — high "Failed" counts are the signal worth investigating.
Yes — the Cron Inspector is fully available in both Lite and Pro.
Complete visibility into WordPress background tasks — so you can stop guessing why things aren't running.
The Cron Inspector is fully available in the free Lite version — no account or payment required.
Pro includes the Cron Inspector alongside all seventeen modules and eight Pro-exclusive deep inspections.