NextJS `withServerActionInstrumentation` marks `redirect()` server actions as internal_error transactions

[smozely]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Have a NextJS Server action that does a redirect inside withServerActionInstrumentation

e.g. this server action

async function serverAction() {
 await withServerActionInstrumentation('serverAction', () => {
 redirect('/foo');
 });
}

Will be marked with a transaction in Sentry that had an "internal_error"

Runnable example (Claude generated, but human validated):

const Sentry = require('@sentry/nextjs');
const nav = require('next/navigation');

const transactions = [];
Sentry.init({
 dsn: 'https://public@example.ingest.sentry.io/1',
 tracesSampleRate: 1,
 beforeSendTransaction(ev) {
 transactions.push(ev);
 return null;
 },
});

async function run(name, body) {
 try {
 await Sentry.withServerActionInstrumentation(name, body);
 } catch {}
}

(async () => {
 await run('redirect', async () => {
 nav.redirect('/login');
 });
 await run('not-found', async () => {
 nav.notFound();
 });
 await run('success', async () => 'ok');
 await run('genuine-error', async () => {
 throw new Error('boom');
 });
 await Sentry.flush(2000);
 for (const t of transactions) {
 console.log(t.transaction, '=>', t.contexts?.trace?.status);
 }
})();

// Output:
// serverAction/redirect => internal_error <-- wrong
// serverAction/not-found => not_found
// serverAction/success => ok
// serverAction/genuine-error => internal_error

Expected Result

Should have not been marked as internal_error

Actual Result

Product Area

Explore

Link

No response

DSN

https://b6d4dd5853e462b70bc0ca053c34e7dc@o4509326989918208.ingest.us.sentry.io/4509331771359232

Version

No response

[linear-code]

ENG-7928

JS-2768

JS-2769

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[smozely]

I'm currently working around it in app code by grabbing the active span on a redirect, setting it to OK and ending it early (so isRecording() is false and the override is skipped), but that's reaching into SDK internals a bit.

[JPeer264]

Thanks a lot for opening the issue and already giving us a reproduction. I just tried it locally with your script and can confirm that the code with the redirect is having the internal_error status.