You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've noticed that at some point Sentry stopped reporting next.js server-side errors on Vercel. I tried example from scratch and only added package-lock.json and debug: true to server-side Sentry config, setup Vercel deployment and I see the same result (example repository)
I open /api/test(1-4) and /ssr/test(1-4) one-by-one and expect to see 8 errors reported, but see only 3.
At the same time if I do npm run build + npm run start locally I see 8 errors reported.
SSR tests 1-3 are a duplicate of #6117. Vercel is doing some weird magic that we haven't gotten round to figuring out yet. Have these errors been reported for you in older versions?
API tests 1-2 are anti-patterns for serverless functions. I recommend putting all your logic inside the handlers. It is impossible for the SDK to flush errors happening outside of the handler scope since we can't top-level await at that point to flush and the serverless function/lambda will freeze/quit.
Have these errors been reported for you in older versions?
Looks like we never had server-side events (only test events from local servers)
Ok, thanks for checking. I will close this issue as a duplicate of #6117 and #6120 just to keep our backlog clean. Our Vercel compatibility is far from the best at the moment and we're looking to improve this in the very near future. Feel free to ping us if you have any more questions.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/nextjs
SDK Version
7.24.2
Framework Version
12.3.0
Link to Sentry event
No response
Steps to Reproduce
We've noticed that at some point Sentry stopped reporting next.js server-side errors on Vercel. I tried example from scratch and only added
package-lock.json
anddebug: true
to server-side Sentry config, setup Vercel deployment and I see the same result (example repository)I open
/api/test(1-4)
and/ssr/test(1-4)
one-by-one and expect to see 8 errors reported, but see only 3.At the same time if I do
npm run build
+npm run start
locally I see 8 errors reported.Vercel logs:
Expected Result
8 errors reported:
/api/test(1-4)
/ssr/test(1-4)
Actual Result
Only 3 events reported:
The text was updated successfully, but these errors were encountered: