[BUG] Server action redirects fail when Next.js 16 cacheComponents is enabled

[ramonmalcolm10]

Are you using the latest version of this library?

• I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

• I have searched the existing issues and found nothing that matches

Describe the bug

When using Next.js 16 with cacheComponents: true enabled in next.config, server action redirects using redirect() from next/navigation do not work. The redirect is not executed and the user remains on the current page.

Reproduction steps

1. Create a Next.js 16 project with this adapter
2. Enable cacheComponents in next.config:

   const nextConfig: NextConfig = {
     cacheComponents: true,
   };
   export default nextConfig;

3. Create a server action with a redirect:

'use server'

import { actionClient } from "@/lib/safe-action";
import { redirect } from "next/navigation";

export const create = actionClient
    .action(async () => {
    // Perform some action
    redirect('/');
});

4. Use the action with useAction:

'use client'

import { useAction } from "next-safe-action/hooks";
import { create } from "./action";

export function MyForm() {
   const { execute } = useAction(create);
   return (
       <button
         onClick={() => execute()}>
         Create
       </button>
   );
}

5. Click the button

Expected behavior

The redirect('/') call should navigate the user to the homepage after the server action completes.

Link to a minimal reproduction of the issue

https://github.com/ramonmalcolm10/next-safe-action-bug

Operating System

macOS

Library version

8.0.11

Next.js version

16.0.0

Node.js version

24.10.0

Additional context

The functionality worked as expected with direct execution.

[programming-with-ia]

I'm working on a similar library, better-next-actions, which aims for a tRPC-like experience for Server Actions, with built-in support for composable middleware and Zod validation.
Any quick ideas or feedback from this community would be hugely helpful!

[nghiepnt-qualgo]

@ramonmalcolm10 Use unstable_rethrow to fix redirects.

next-safe-action/packages/next-safe-action/src/hooks.ts

Line 61 in 497688f

if (FrameworkErrorHandler.isNavigationError(e)) {

This may be helpful for your PR addressing the issue. I'm not certain since this is an unstable feature with unclear version support.

[programming-with-ia]

@ramonmalcolm10 @NghiepNgo-Qualgo
see: #393 (comment)

[markedwards]

We are noting similar behavior post-Next-16, and we do not have cacheComponents: true. It is difficult to reproduce it on demand, but sometimes in production server action redirects will simply stop working with no server-side error, as if the redirect is simply being ignored by the client.

And we note this in the browser console:

Uncaught (in promise) Error: NEXT_REDIRECT

Refreshing the page remedies the issue and redirects work again until the next time it happens.