Section
Troubleshooting
Recover from failures, debug edge cases, and understand what to check next.
In this section
Browse the public pages here.
-
Troubleshoot Startup and Modules Troubleshooting
Diagnose first-run module registration, dependency, configuration, route, static asset, docs surface, and package-choice failures.
-
Failed Form UX Guide
RazorWire-enhanced forms now have a convention for server failures. A form with `rw-active="true"` gets request markers, a default form-local fallback UI for unhandled failures, server-side helpers for high-quality validation errors, and development diagnostics for anti-forgery failures.
-
Durable contract diagnostics Guide
AppSurface Durable uses append-only `ASDURxxx` codes. Messages and operator history must contain safe Problem, Cause, Fix, and Docs guidance and must never include credentials, provider response bodies, tokenized URLs, email content, or child-sensitive data.