@sentry/nextjs v8 does not create issue/error on vercel for API Route Handler

[TuanManhCao]

@sentry/nextjs v8 does not create issue/error on vercel for API Route Handler

[lforst]

@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 waitUntil will solve our problems. To me this seems to be a bug in Vercel that needs to be figured out.

[s1gr1d]

Hello, thanks for reaching out! Do you start your app with next dev or next start? Does the error show up in Sentry if you run the local production build with next build and next start?

[TuanManhCao]

Thanks @s1gr1d .

I just tried to do a next build then do a next start on my local machine and do see error getting tracked in sentry

As you can see in this screenshot, the env is production, and the host is localhost:3000

[lforst]

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 waitUntil but that seems buggy right now so I reached out to Vercel directly. I hope they will clear things up but this is definitely top of my mind.

[TuanManhCao]

Thanks @lforst ! Wondering if this is particular to vercel or just new version of @sentry/nextjs? Or combination of both?

[TuanManhCao]

@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!