500 caused by 413 FUNCTION_PAYLOAD_TOO_LARGE does not get reported to Sentry in Next.js & Vercel integration

[AbhiPrasad]

Discussed in #7944

^{Originally posted by dmudro April 24, 2023}
I have a specific case in my Vercel / Next.js / Sentry integration, where a 500 is not reported to Sentry.

the particular edge case is that my page occasionally fails on 413 Vercel / AWS Lambda payload limit. I do see the 500 in my Lambda logs (outside Sentry) but as if this particular failure never reached the Sentry notification trigger in my app handler / integration.

while I might need to understand the integration in more detail, I wonder if this is a known limit or I am having my withSentry Next.js / Vercel integration incorrect. I do see my custom Next.js 500 page when manually replicating the issue which is confusing as I'd expect this to be caught by Sentry. other 500s get reported to Sentry as expected.

overall the integration works pretty well.

[lforst]

I think since the SDK is inside the application layer and this error happens on the infrastructure layer and there is no way to access that information, I think we can't do anything here.

The solution for error monitoring here would be to monitor the logs. I don't think this is currently possible with Sentry.

[AbhiPrasad]

@dmudro I think for now we can't make this work, so closing, but I think we can revisit in the future!