Luca Forstner

@marcosdiasdev I would like to reiterate, this issue needs reproduction. To look into this further, we need a way to reproduce this error. Please provide a stackblitz or github repo,...

@pieterbeulque awesome thanks! I'll take a look.

Update: We're gonna move back to the classic runtime because we discovered issues with a non-faulty fix. The "fix" we merged actually did nothing because I made a mistake while...

@AbhiPrasad would love to hear your thoughts on having 2 spans, one for total duration, one for time to first byte (not the web vital lol). Would this have downstream...

> Could span attributes be an alternative to emitting more spans? Yes that makes absolute sense. We should do it like this.

Hi, can you share how you are throwing errors that are not logged? Thanks!

Where are you calling `requiredAuth`? In a server component? Api route? Route handler? App dir, pages dir?

Would you mind giving a small but complete example? Please verify that this is not your issue: https://docs.sentry.io/platforms/javascript/guides/nextjs/#:~:text=Errors%20in%20Nested%20React%20Server%20Components (section "Errors in Nested React Server Components")

Yeah okay, that error should definitely be reported. I tried to reproduce with a server component like yours: ``` export const dynamic = 'force-dynamic'; export default async function Page() {...

If you add ``` beforeSend(event, hint) { console.log(event.exception?.values); return event; }, ``` Do you see anything in the logs?