Next.js v15.4.0+ does not report errors in route handlers

[mjq]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.8.0

Framework Version

Next 15.5.2

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Create a Next.js app with pnpm create next-app@latest my-app
2. Add Sentry using the wizard (pnpx @sentry/wizard@latest -i nextjs --saas --org YOUR_ORG_HERE --project YOUR_PROJECT_HERE)
3. Run with pnpm run dev, navigate to /sentry-example-page, and click the button

Expected Result

SentryExampleFrontendError and SentryExampleFrontendError issues are created in Sentry

Actual Result

Only the SentryExampleFrontendError issue is created. The SentryExampleFrontendError error is not reported to Sentry.

[linear]

JS-898 Next.js v15.4.0+ does not report backend errors

[mjq]

This is almost certainly caused by vercel/next.js#82612. When OTel is enabled, Next isn't calling its onRequestError hook, so Sentry.captureRequestError is never called. Since the Sentry SDK enables OTel, it triggers this bug. According to that issue, this has been broken in Next since v15.4.0.

This appears to be an upstream bug. I don't know if there's anything we can do to work around this in the meantime.

[mjq]

I confirmed that the bug started with version 15.4.0: the prior version (15.3.5) correctly creates both issues, while 15.4.0, 15.4.7 (last of the 15.4.x line), 15.5.0 and 15.5.2 (latest) all fail to create the backend issue.

[chargome]

Adding to this: This issue only affects errors thrown in route handlers with turbopack builds atm, as we do not have any kind of build-time wrapping there.

[chargome]

https://github.com/vercel/next.js/releases/tag/v15.5.1-canary.25 contains the fix for this

[ThangBui2703]

Does anyone find the way to fix this issue??

[RulaKhaled]

Hey @ThangBui2703, did you try to bump nextjs version to v15.5.1-canary.25?