-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@sentry/nextjs v8 does not create issue/error on vercel for API Route Handler #12045
Comments
Hello, thanks for reaching out! Do you start your app with |
Thanks @s1gr1d . I just tried to do a As you can see in this screenshot, the env is production, and the host is |
Hi, I just looked into this and my suspicion is that Vercel is freezing lambdas before we are able to flush out events. I looked into using |
Thanks @lforst ! Wondering if this is particular to vercel or just new version of @sentry/nextjs? Or combination of both? |
@TuanManhCao I am honestly not sure. It might be that vercel changed something or that the SDK now requires a tad longer to flush, causing us to run into the limit. I am optimistic however that using |
@lforst it's awesome to see that this issue is resolved so quickly. Thanks Luca! Can you elaborate a little bit more? As in, do I need to do anything on my side to make this work? Or should I just wait for next version coming out? If yes, which version I should be looking out for? Thanks! |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
8.0.0
Framework Version
nextjs ^14.2.3
Link to Sentry event
No response
SDK Setup
my nextjs config
Steps to Reproduce
When i visit /api/sentry-example-api on localhost I see the error is tracked correctly in my sentry's dashboard's issues
However when I deployed the code to vercel cloud, I checked that the source map is uploaded correctly, the env variable for dsn, auth_token, all setup correctly (via console.log())
Step to reproduce:
/api/sentry-example-api
I saw the page show 500 error, checked vercel log, it does thow the errorAll work well in local env.
And strange thing is the client code for tracking error is working, meaning this page (see screenshot)
Any idea?
Expected Result
The error for API route should show up in sentry dashboard
Actual Result
Right now the error does not show up in sentry dashboard
The text was updated successfully, but these errors were encountered: