Turn it on
- Go to WooCommerce → Powerups and switch on Cron inspector in the Developer group.
- Click Configure, then the Cron events tab.
The Cron events tab with an overdue event and the Loopback card
Status
The top of the tab shows Due now, Overdue, Events and Stored size, plus:- WP-Cron: on (runs on page visits), alternate cron (
ALTERNATE_WP_CRON), or off (DISABLE_WP_CRON, a server cron job runs it). - Cron run: not running, running, or last started and didn’t finish cleanly.
- Oldest overdue: the hook and how late it is. An event counts as overdue when it’s more than 10 minutes late.
- A warning when the stored cron list is over 500 KB. WordPress loads it on every page, so look for hooks with many events.
Loopback
Check loopback (Safe) sends a request from your server to its ownwp-cron.php. It tells you the site can reach itself, not that events run: on PHP-FPM hosts, wp-cron.php answers before anything runs, so the check passes even when cron itself fails. The result is kept for 12 hours.
The events list
Every event, 50 per page, with Hook, Next run and Schedule. Filter by All events, Due now, Overdue or No callback, or search by hook name. Details shows the callbacks and the event’s arguments.- Each event shows its owner: WordPress, WooCommerce, a plugin, a theme, or “Probably …” when it’s a guess.
- No callback: no callback was found in this request. This is a hint, not proof: some plugins only add their callback while cron runs.
- Arguments under names like token or password are shown as
[masked]. Arguments without names are shown as they are.
Run now
Run now never runs the event inside your page. It hands the event to WP-Cron and starts a cron run in the background.
The result says what happened: a cron run started, WP-Cron is off so the server cron runs it, it runs on the next page visit, cron is already running, or it couldn’t start.
Events that belong to WordPress or WooCommerce work the same way, but for them Run now… is Advanced, due or not: type “run” to confirm. Running them early can publish scheduled posts, cancel unpaid orders or start sales. On multisite only a network (super) admin gets this button.
Action Scheduler’s queue, Admin Powerups’ own jobs and hooks a site filter protects have no Run now. They run on their own schedule.
A legend above the list shows these levels, and says so when your account can’t run WordPress or WooCommerce events or delete events.
Delete
Deleting is Advanced: type “delete” to confirm. On multisite only a network (super) admin can delete.- Delete or Delete selected: up to 20 events at a time. A recurring event stops repeating unless its plugin schedules it again.
- Delete all (under Hooks with no callback): every event of a hook whose plugin or theme is inactive or no longer installed.
When the list is read-only
If another plugin handles cron storage on your site, the list is read-only and may not match what really runs. Use that plugin’s tools to change events.Data
On phones
On a phone, each event stacks into a block instead of scrolling sideways.Known limitations
- If another cron run saves at the same moment, a deleted or moved event can come back. The message says so. If a move can’t be finished or undone, the message says the event may run twice.
- Events whose stored data doesn’t match their key can’t be changed safely, so they’re refused.