Diagnose an opaque HTTP error

Steps

Record the safe reference, timestamp, route, and selected environment. An authorized operator inspects the matching server error entry without exposing secrets or a stack trace to the browser.

browser: safe error + reference
operator: correlate local logs → classify failure
          configuration | permission | storage | provider | application bug

For 419, refresh/login and obtain a current token. For 429, wait for the documented window rather than retrying rapidly. For AI 502/timeout, do not retry automatically: the provider may have processed the call and its reservation remains consumed.

Verify

Test that a malformed request receives a safe status, no-store headers, and no internal paths or provider body. See Troubleshooting.

Editorial provenance

Source: resources/guides/error-reference.md. Source SHA-256: 5f9fa4e81c2824b15350725b9580e3530318ad2c19b691390dfa3fca4a46151f.

Knowledge-base application source; editorial checkpoint 2026-10-20. See candidate status and adoption boundary.