SleekPixel reads the wp_actionscheduler_actions table, which has been stable since Action Scheduler 3.0. Older versions used custom post types instead, which the integration does not target. Since WooCommerce 4.0 forces Action Scheduler 3.x, any reasonably current WooCommerce install is fully supported out of the box.

A select count(*) from wp_actionscheduler_actions where status equals complete and last_attempt_gmt greater than now minus 24 hours. The query uses the existing status and last_attempt_gmt indexes added by Action Scheduler itself, so the count returns in well under 50 milliseconds on million row tables that WooCommerce stores routinely accumulate.

Yes. The template accepts an optional group filter that adds a join to wp_actionscheduler_groups and a where clause on the group slug. Useful when a post focuses on order processing rather than the whole queue. A WooCommerce subscriptions post might scope to woocommerce-subscriptions for a more relevant headline number.

The default formatter uses Intl.NumberFormat style abbreviated when counts pass 10,000, rendering as 84k or 1.2m, with full digits below that threshold. You can switch to full digits at every scale via a template setting, which is useful for posts where the exact count is the point of the story rather than a rough magnitude.

No, pending strictly means status equals pending in wp_actionscheduler_actions. Failed actions sit in status equals failed and canceled actions in status equals canceled, both excluded from the pending slot. Add a second template variant if you want a card that highlights failed counts as a separate red badge.

Yes, because the count window is rolling 24 hours by default and most teams configure Action Scheduler to keep at least 30 days of history. If you purge inside the 24 hour window the count drops accordingly on the next TTL refresh, which is the honest behavior since the actions are no longer on the system.

Yes. Tools like the Action Scheduler high volume admin or third party queue inspectors read the same wp_actionscheduler_actions table that SleekPixel queries. They coexist without conflicts because SleekPixel never writes to the queue or modifies its schema. Both layers operate independently on top of the same underlying data.

Out of the box the template renders a single 24 hour number, not a trend line. A trend variant exists in the SleekPixel template library and renders a small sparkline alongside the headline number. It pulls a per-day grouped count for the last 14 days, cached more aggressively due to the heavier query cost.