About this plugin
QueueRay is a read-only diagnostic dashboard for WordPress sites that use Action Scheduler, including many WooCommerce stores.
Instead of showing only raw failed and past-due totals, QueueRay groups active problems by hook and adds a conservative diagnosis:
- what kind of background workflow the hook appears to represent;
- which plugin likely owns it;
- whether ownership came from a registered callback or a naming heuristic;
- what may be affected if the problem continues;
- what to inspect before retrying, canceling, or deleting queue data.
QueueRay does not delete, retry, cancel, or edit scheduled actions.
Current features:
- Action Scheduler queue totals and past-due counts
- Failed actions in the last 24 hours and 7 days
- Diagnosis cards for active failures and overdue hooks
- Conservative impact categories for payments, subscriptions, marketing sync, analytics, email, shipping, integrations, and unknown jobs
- Historical failed rows are not promoted into active diagnoses unless the same hook failed in the last 24 hours
- Likely-owner detection from registered callback source files when available
- Naming heuristics as a fallback, with explicit confidence
- WP-Cron and Action Scheduler queue-runner signals
- Estimated standard Action Scheduler table size
- Privacy-conscious support report that excludes action arguments and Action Scheduler group names
- Reserved QueueRay QA fixtures are excluded from health severity, diagnosis cards, operational totals, and hook rankings
Why read-only?
Deleting a failed or overdue background job without understanding what owns it can hide a symptom or interfere with plugin workflows. QueueRay diagnoses first and leaves queue changes to the site owner or developer.
What does “possible impact” mean?
QueueRay intentionally uses cautious language. A hook name can suggest that a job relates to payments, subscriptions, analytics, marketing sync, or another workflow, but it cannot prove that a customer-facing feature is broken. Always inspect the affected Scheduled Action log before making changes.
Privacy
3 does not transmit data externally. The copyable support report excludes Action Scheduler action arguments and group names because either can contain plugin-specific identifiers.