- Ya
- 27 Agosti 2026, 16:17 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 483b665
The status endpoint is asked before the UI offers a network query, so a practice that is not onboarded sees an explanation instead of a button that always fails. That was the intent in the javadoc; the endpoint answered with a bare connected:false and no explanation, so the panel could only say "not connected". "Not connected" reads as an outage to wait out. The actual reason -- this practice has no QHIN onboarding and the certificate it issues -- is something somebody can act on, and it already existed on the refusal. It was just only ever shown to whoever tried, never to the person deciding whether to. unavailableReason() rides the status response, and the field is omitted entirely when connected so a panel cannot render a stale explanation beside a working network.