Diagnostics and reachability
The plugin's self-report: what cannot be delivered with the current configuration, and why.
updated
Outline — facts still to be confirmed
This article is a structured outline. Its headings and scope are settled; the
specific values, screens and steps are marked TODO(owner: verify)
until they have been checked against the plugin itself. Blueprint §7 is explicit
that no article may state plugin behaviour that has not been verified.
Diagnostics answers one question: given the current configuration, what cannot arrive? It makes no network calls; it reasons about the configuration.
Finding types
| Finding | Meaning |
|---|---|
NO_ROUTE |
Nothing is configured that could carry this event. |
UNREACHABLE_CONFIG |
Configured, but the combination cannot deliver. |
MISSING_REQUIRED |
The operator asked for something and a required value is absent. |
POSTURE |
A configuration choice worth knowing about, not an error. |
MISSING_REQUIRED exists because of a specific lesson: an incomplete configuration is the
most important thing to report, never a reason to stay quiet. Silently skipping an adapter
that is not fully configured hides exactly the case the operator most needs to see.
Findings are surfaced in Diagnostics, in an admin notice, and as log rows with the
unreachable status. They are evaluated when settings are saved, on a daily schedule, and on
demand, and individual findings can be dismissed.
Two known findings you may see today:
- Google Ads Enhanced Conversions are not sent yet, reported whenever an Ads conversion ID is configured.
- Non-ASCII identifier fields omitted on hosts without
mbstring, naming the affected fields.
Outline still to fill
TODO(owner: verify) — the full finding catalogue with the exact on-screen wording, and what each one recommends.
Was this page helpful?