Skip to content

April 12, 2026: Crash reporting and support correlation

  • Added a direct Report issue path on route and boundary error states so users can send Sentry feedback against the exact crash event.
  • Added safer support-correlation details behind the scenes, including request IDs, Sentry event IDs, and support codes where available.
  • Hardened Sentry privacy defaults so replay remains masked and captured strings redact common secrets, cookies, bearer tokens, and email addresses before they are sent.

When something breaks, customers need a clear next step and support needs enough context to trace the problem fast. This update gives users an immediate reporting path after a crash while keeping the captured data conservative and support-friendly.