Catch async errors

I need to make sure uncaught promise rejections in the signup flow surface to Sentry and don’t leave the UI stuck. Wrap the async functions that run when the user clicks Create Account so the submit button is re-enabled and an error banner appears, then forward the error to Sentry, and do this before the end of today.

Before I ship, make it obvious to a reviewer how an async failure behaves: show the user-facing error message first, then the retry button, and below that the telemetry call to Sentry. Highlight any places where the UI might remain blocked or state left inconsistent.

The Create Account button was clicked, the spinner started, and an uncaught rejection hit in the network code; now the spinner never stops and I can’t find the error in Sentry. I’m worried the button state and local store are inconsistent and I’m missing where the rejection is thrown. What’s the likely root cause and the least risky next fix to restore user experience and capture the error?

Across several releases we keep getting one-off crashes tied to different async handlers: WebSocket reconnects, file uploads, and form submits. I spend time reproducing, patching, and then another slips through. What habit and guardrail should I adopt to stop these leaks, and how do I add a simple checklist so every async entry point has consistent error capture and state rollback?