Begin with the exact symptom and the smallest safe observation. A version label, green dashboard indicator, queued message or successful source test does not independently prove the corresponding live workflow works.
Capture an identifiable baseline
Record installed Free/Pro versions, active theme and child theme, WordPress/PHP versions, schema readiness, timezone, locale and UTC timestamp. When comparing a checkout and release package, record the source commit and package SHA-256 separately; the same product version can still contain different bytes.
Describe the route pattern without its secret query values. Add viewport/browser for a presentation issue, relevant cache layers, cron mode and the last known working state. Keep production configuration and credentials out of the report.
Inspect the matching subsystem
| Symptom | Useful safe evidence |
|---|---|
| Contact unavailable | Saved intake/readiness reasons, recipient present, notice/URL and Page status |
| Newsletter pending | Request/confirmation state, token age, redacted transport result |
| Booking/payment mismatch | Booking status versus settled ledger and attempt state; amount/currency |
| iCal stale | Source label, last success, next due, bounded error class |
| Privacy incomplete | Native request ID, retained/manual reason, current review/progress state |
| Theme issue | Surface/template, active theme, layout conditions and relevant cache |
Use WordPress Site Health and the product panels that actually exist in the installed build. Do not invent a universal status screen or assume a missing source/check was run. Do not copy full feed URLs, bearer links, raw mail bodies or complete provider payloads.
Classify before changing
Separate product defects, configuration faults, environment/transport failures and missing evidence. Examples include a disabled intake, stale form, unsupported payment currency, unavailable cron, invalid activation identity or a historical test assertion pinning old metadata.
A passing test with doubles is not provider E2E; a local mail sink is not Internet delivery. A failed historical assertion remains failed until repaired in its owner scope. State PASS, PARTIAL, NOT RUN and the actual observed failure distinctly.
Share a focused report
Provide reproduction steps, expected/actual result and a redacted evidence excerpt. Keep an operational backup before any data-changing repair. Inspect current state before clearing caches or resubmitting; doing so can erase the condition you need to diagnose.
See safe conflict testing for isolated reproduction and booking/payment recovery for uncertain financial outcomes.
