Background job monitoring — no silently stalled queue.
Relvato checks your WordPress Action Scheduler queue is actually draining — catching the stalled or stuck jobs that quietly stop order emails, subscription renewals and stock sync.
- ✓The Action Scheduler queue is draining, not growing
- ✓No jobs stuck ‘in-progress’ past their runtime
- ✓The pending backlog is within a healthy bound
- ✓Flags the stalled job groups
WooCommerce and half your plugins rely on background jobs. When the queue stalls — a fatal in a hook, a killed cron — everything that depends on it just stops, with no error you’d notice. Relvato watches the queue depth and age so you catch it in time.
On WordPress, a stalled or jammed Action Scheduler queue has a one-click fix in WordPress → Relvato: the plugin runs the queue once — only jobs that were already due, for a few seconds — which also releases jobs stuck mid-run and clears jobs whose plugin was removed. If WP-Cron is switched off on the site, the fix says so, because that's why the queue would stall again.
- The plugin reads your Action Scheduler queue — pending, in-progress and failed counts and ages.
- Flags a growing backlog or jobs stuck past their expected runtime — the signature of a broken cron.
- Runs on a schedule and on change, so a stalled queue is caught before customers notice missing emails.
What breaks when the queue stalls?
Order emails, subscription renewals, stock sync, and anything else scheduled — often silently.
Does it need the plugin?
Yes — reading the Action Scheduler queue state needs the WordPress plugin.
Can Relvato unstick the queue?
Yes, with the Relvato plugin: one click in WordPress → Relvato runs Action Scheduler's own queue runner once, for jobs that were already due. It also tells you when WP-Cron is switched off on the site — the usual reason a queue stalls in the first place.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.