QueueRay – Background Job Diagnostics
Understand recent Action Scheduler failures, overdue jobs, likely owners, possible impact, and what to inspect next — without changing queue data.
Use with caution
QueueRay works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where QueueRay stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| action scheduler | >100 |
| cron | >100 |
| diagnostics | >100 |
| scheduled actions | >100 |
| woocommerce | >100 |
About QueueRay – Background Job Diagnostics
From the official readme · v0.5.3Description
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
QueueRay 0.5.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.
Installation
- Upload the
queuerayfolder to/wp-content/plugins/, or install the ZIP from Plugins > Add New > Upload Plugin. - Activate QueueRay.
- Make sure WooCommerce or another plugin that loads Action Scheduler is active.
- Open Tools > QueueRay.
- Review the scan and, when useful, copy the diagnostic report.
Frequently asked questions
Does this plugin repair failed scheduled actions?
No. QueueRay is intentionally read-only. It helps you understand what is failing before you make changes.
Does it require WooCommerce?
No. It requires an active Action Scheduler instance. WooCommerce is one common source of Action Scheduler.
Does it send site data anywhere?
No. QueueRay runs locally in WordPress and does not make external API calls.
How does owner detection work?
When a scheduled-action hook has a callback registered on the current request, QueueRay attempts to map the callback source file to an installed plugin. When that evidence is unavailable, it uses conservative hook naming heuristics and then lower-confidence group naming heuristics. Ownership is always shown as likely rather than certain.
Why can old failed actions exist on a healthy site?
A failed row can remain in Action Scheduler after the underlying issue has recovered. QueueRay separates recent failures from historical failed rows so a large old failure total is not automatically treated as a current outage.
Why can WP-Cron be disabled without being an error?
Some hosts disable WordPress’s traffic-triggered cron and replace it with a real server cron. QueueRay reports this cautiously because it cannot verify an external scheduler from inside WordPress.
How are QueueRay development fixtures handled?
Actions in the reserved queueray-fixtures QA group, including recognized suffix variants, are excluded from operational health severity, diagnosis cards, operational queue totals, and top-hook rankings. When fixtures are present, raw Action Scheduler totals remain visible only in the support report for comparison. Real non-fixture failures and overdue actions are still diagnosed normally, including when they use the same hook names as fixtures.
Changelog
0.5.3
- Updates the WordPress.org tested-up-to metadata for WordPress 7.1.
- No diagnostic behavior or queue-writing behavior changed.
0.5.2
- Renames the plugin to QueueRay – Background Job Diagnostics.
- Aligns the plugin slug, text domain, admin identifiers, and release metadata with
queueray. - Keeps the diagnostic behavior read-only and otherwise unchanged.
0.5.1
- Excludes reserved QueueRay QA fixtures from health severity, diagnosis cards, operational queue totals, and top-hook rankings.
- Preserves raw Action Scheduler totals in the support report so test environments remain auditable.
- Correctly separates real actions from fixtures even when they share the same hook name.
- Samples beyond fixture-heavy queue rows while keeping scan work bounded.
- Groups diagnoses at hook level to prevent duplicate or overlapping counts across Action Scheduler groups.
- Reports unsupported exact fixture or active aggregates as n/a with a warning instead of promoting raw test data or claiming a healthy queue.
- Improves admin accessibility with labeled report output, scoped table headers, and readable release CSS.
- Localizes clipboard status messages and hardens callback-source inspection for invokable objects.
- Simplifies the public plugin name to QueueRay and synchronizes release metadata.
0.5.0
- Adds a development-fixture notice for local QA data.
- Simplifies diagnosis cards by moving Action Scheduler group slugs out of the primary non-technical view.
- Renames owner wording to “Likely source” and “Source confidence” to reduce false certainty.
- Broadens read-error handling to PHP Throwables so an unexpected store or runtime error is less likely to break the diagnostics page.
- Keeps all scans read-only, local, and free of external requests.
0.4.0
- Adds an at-a-glance decision summary and moves raw queue details into an expandable technical section.
- Caps exact per-hook follow-up queries to the eight displayed buckets, reducing worst-case database-query amplification on large, diverse queues.
- Separates hook-based owner evidence from lower-confidence group-only heuristics.
- Adds transparent sampling notices when more than 150 recent failures or overdue actions exist.
- Keeps overdue severity age-aware so a large but freshly late queue is not marked high priority from count alone.
- Removes Action Scheduler group names from the copied support report for stronger privacy defaults.
- Adds scan-duration metadata for performance troubleshooting.
- Removes the placeholder Plugin URI from the production header.
0.3.1
- Keeps the “Top failed hooks” table aligned with the 24-hour active-failure window.
- Historical failed rows remain in Failed total but no longer appear under a recent table label.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best QueueRay alternatives
All action scheduler plugins →
FAQ
QueueRay: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 7, 2026
Is QueueRay free?
Yes. QueueRay is free to download and use from the official WordPress.org plugin directory.
Is QueueRay safe to use in 2026?
QueueRay works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
How many websites use QueueRay?
QueueRay is active on <10 WordPress websites and has been downloaded 138 times since it launched in August 2026. It was downloaded 69 times in the last 30 days.
Does QueueRay work with WordPress 7.1?
Yes. The developer has tested QueueRay up to WordPress 7.1.3, the latest release. It requires WordPress 6.4 or newer.
What PHP version does QueueRay need?
QueueRay requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was QueueRay last updated?
The latest version, 0.5.3, was released on August 30, 2026 (1 month ago).
Who makes QueueRay?
QueueRay is developed and maintained by delacooa12.
What are the best alternatives to QueueRay?
The most popular alternatives to QueueRay are ZS Action Scheduler Optimiz… (300+ installs), Advanced Cron Scheduler for… (100+ installs) and Failed Actions Monitor for… (20+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
