Fix Sentry capturing notFound as errors

[sentry]

This PR addresses an issue where Sentry was reporting false positive errors due to TanStack Start's notFound() control flow.

TanStack Start uses throw { isNotFound: true } as a mechanism to signal a 404 state, which is not a true error but a control flow. Sentry's server-side middleware was indiscriminately capturing these thrown objects as exceptions.

The fix involves modifying src/instrument.server.mjs to wrap the beforeSend function. The wrapper now checks if the thrown exception (hint.originalException) has an isNotFound property set to true. If so, it returns null, preventing Sentry from reporting it as an error. Otherwise, it delegates to the original redactByokRequestHeaders function.

Fixes TANSTACK-COM-4QS

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	tanstack-com	1a67335	Commit Preview URL Branch Preview URL	Aug 29 2026, 11:03 PM