next/redirect-outside-try

Why

redirect(), permanentRedirect(), notFound(), forbidden() and unauthorized() throw a special error that Next.js catches to change the response. Inside a try whose catch handles every error, that signal is caught by your code instead: the user stays on the page, sees a generic error message, or the action reports a failure after it succeeded.

Fix

Do the risky work inside try, keep the result in a variable, and call redirect() after the try/catch. If the call must stay inside, call unstable_rethrow(error) first in the catch, or rethrow what you do not handle.

Examples

// bad
try { await createPost(data); redirect('/posts') } catch (error) { return { message: 'Could not save' } }
// good
try { await createPost(data) } catch (error) { return { message: 'Could not save' } }
revalidatePath('/posts')
redirect('/posts')

Sources

• Next.js docs, redirect (behavior)
• Next.js docs, unstable_rethrow

Read it in the terminal

npx github:dawidolko/frontend-skills explain next/redirect-outside-try