How are you capturing exceptions using Next.js (13/14) server actions?

[phstc]

Is there any generic wrapper (for TypeScript) that can be used with server actions, or should I use a regular try...catch...Sentry.captureException?

"use server";
export async function doesSomethingById({ id }: { id: string }) {
 // this and that
}

[lforst]

We have a wrapper for server actions! https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#instrument-nextjs-server-actions

[lforst]

Is it only for instrumentation or does it capture errors too?

It also captures errors!

Is there something automatic for server actions, a Next.js catch-all so we don't need to add it per action?

Unfortunately, this is a limitation by Next.js. There is no global error handler that we can abuse to collect throwing actions. Also, auto-instrumentation is very hard and extremely error-prone (to the point where we are not gonna do it), because of all the bundling magic that happens. We would have to build a Next.js server actions compiler, which is not something that seems reasonable to do. However, we are in close talks with Vercel to make a global error hook inside instrumentation.ts happen!

[phstc]

@lforst thank you for the explanation!

However, we are in close talks with Vercel to make a global error hook inside instrumentation.ts happen!

That's exciting! 🙏

return await Sentry.withServerActionInstrumentation(

What else withServerActionInstrumentation does? I would be comfortable with withServerActionCaptureException or serverActionExceptionWrapper.

Is there any chance that because of some Sentry limit/issue or my account running of credits for instrumentation, my code won't execute?

[lforst]

It captures spans for distributed tracing and sets some tags and extra data that may be useful to you. Your code will always run! If it didn't based on quota or limit that would be extremely dumb (which we hopefully aren't 😂).

[phstc]

I know! 😅

I don't remember the exact version, but if my memory is not failing me, I believe I had an issue with the Sentry SDK throwing errors in the past because of a misconfiguration.

[lforst]

Ironically, we cannot rule out bugs.