[BUG] using notFound() in server action is handled as successful action

[maltesa]

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

The following code logs Success. to the browsers console.

// action.ts
export const userAction  = userActionClient.action(async () => {
  notFound()
})

// Component.tsx
// ...
  const { execute } = useAction(updateAssignmentSettingsAction, {
    onSuccess: () => console.log('Success.'),
    onError: () => console.log('Error'),
  })

Reproduction steps

Call notFound() in a server action.

Expected behavior

I expected the onError callback to fire.

Link to a minimal reproduction of the issue

none

Operating System

macOs

Library version

7.10.4

Next.js version

15.1.5

Node.js version

22

Additional context

No response

[IPJT]

Same thing if the device looses network connection. Seems very weird

[TheEdoRan]

This is the correct behavior for all next/navigation functions at the moment, but I can understand that it might be confusing because users expect notFound() and forbidden() to trigger onError() instead. However, I believe redirect() should continue to trigger onSuccess() (as has already been explained in various issues/discussions in the past). What do you think? I could make notFound() and forbidden() trigger onError() in v8, which would be a breaking change.

[maltesa]

Yes, right. Didn't think about, that redirect throws too.

What do you think? I could make notFound() and forbidden() trigger onError() in v8, which would be a breaking change.

That sounds sensible to me. I would love to see it in the v8.

Thank you for this great library 👍