WordPress Queue Inspector
Collect WP-Cron and Action Scheduler evidence into a local incident workspace, investigate queue problems, compare captures, and prepare a privacy-reviewed handoff.
The problem it solves
WordPress Queue Inspector A local incident workspace for WP-Cron and Action Scheduler evidence. It never runs, deletes or reschedules jobs. Bring in read-only snapshots, see cautious findings, and document what changed. It uses only the Python standard library for analysis and a WP-CLI bootstrapped PHP exporter for collection.
Who WordPress Queue Inspector is for
- Developers and maintainers who need reviewable evidence before changing or releasing software.
- Users working with WordPress, Action Scheduler, WP-Cron who want the documented v1.0.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Collect WP-Cron and Action Scheduler evidence into a local incident workspace, investigate queue problems, compare captures, and prepare a privacy-reviewed handoff.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.0.0
Capabilities below come from the current project README and release documentation.
A local incident workspace for WP-Cron and Action Scheduler evidence. It never runs, deletes or reschedules jobs. Bring in read-only snapshots, see cautious findings, and document what changed. It uses only the Python standard library for analysis and a WP-CLI bootstrapped PHP exporter for collection.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Linux
Built with
- Python
- PHP
- JavaScript
- WordPress
- Action Scheduler
Changelog
Release notes from the canonical v1.0.0 source tag.
- Initial snapshot schema, read-only WP-CLI exporter, offline CLI and browser incident view.
- Coverage-aware findings, cautious claim evidence, before/after comparison and follow-up diagnosis; shared state/age/group filters in CLI and browser.
- Redacted HTML/Markdown/JSON reports, multi-capture history, browser selection persistence, editable incident notes, and portable hash-checked incident ZIP backup/restore.
- Strict import field validation, partial evidence on collector read errors, and explicit total job/log bounds.
- Unit, PHP collector failure/boundary, disposable WordPress, browser and independent product checks. Platform and integration limits are listed in TESTING.md.
Quick start
The shortest documented path into the current release.
Before running these source commands, download the v1.0.0 source archive, extract it, and open a terminal in the extracted project folder containing README.md. Follow the tagged README for required runtimes and any platform-specific setup.
Python 3.10+:
python3 -m wqi inspect samples/baseline.json
python3 -m wqi jobs samples/baseline.json --state failed --min-age 60 --group-by hook
python3 -m wqi compare samples/baseline.json samples/followup.json
python3 -m wqi new ./my-incident samples/baseline.json samples/followup.json --notes 'Runner checked separately'
python3 -m wqi add ./my-incident samples/latest.json
python3 -m wqi note ./my-incident 'Follow-up reviewed' --append
python3 -m wqi history ./my-incident
python3 -m wqi compare ./my-incident --baseline-index 1 --followup-index 2
python3 -m wqi report ./my-incident --format html --output report.html
python3 -m wqi backup ./my-incident my-incident.zip
python3 -m wqi restore my-incident.zip ./restored-incident
python3 -m wqi serve ./my-incidentOpen http://127.0.0.1:8765/ for the searchable, paginated local browser view and report. The server binds to loopback only; Ctrl-C stops it. Use add to append later snapshots. The history command lists capture indices; comparisons must use an older baseline and later follow-up. Use backup and restore for a portable ZIP. incident.json contains SHA-256 checks for every snapshot file; a restored copy is verified on open. Reports are intended for review before sharing.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
The current v1.0.0 release is bounded by the behavior documented in its README and changelog. It does not claim unsupported platforms, automatic interpretation, or results beyond the evidence it produces.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
No privacy behavior beyond the current repository documentation is claimed. Review the source, security policy, and input/output behavior before using sensitive material.
License and release
WordPress Queue Inspector is published under MIT. The current cataloged release is v1.0.0, published 2026-11-02.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
WordPress Queue Inspector v1.0.0
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: 01d3d8896ef60bbf.