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
For schema-11 runtime heartbeat maintenance, use the [retention operations guide](../Durable/heartbeat-retention-operations.md#recover-and-diagnose) and its [complete runtime-set receipt checklist](../Durable/heartbeat-retention-operations.md#complete-runtime-set-preflight-and-proof-checklist). A pending migration 0011 preflight means the downtime migration has not been applied; drain workers, apply it as migration owner, reconcile the complete reviewed manifest, then require one passing preflight under each distinct runtime credential. A migration advisory-lock, runtime-fence, or index table-lock timeout keeps activation closed until the blocker is resolved and the entire gate is rerun. The role recipe may refuse observed drift; follow the category-specific direction below and use a reviewed repair. Repeated prune failures mean inspect database reachability and exact grants, then retry or pause via a new provider registration. Cleanup failures alone do not change Work readiness.