Error Handling with next-safe-actions in React-Query: Errors Resolving as Data or Not Caught

[AndonMitev]

This is my server action:

export const getTasks = actionClient
  .metadata({
    actionName: 'getTasksAction',
  })
  .action(async ({ ctx: { jwt } }) => {
    const url = `${env.NEXT_PUBLIC_APP_BASE_URL}/mocks/mocked_tasks.json`;
    const options: RequestInit = {
      cache: 'no-cache',
      headers: {
        Authorization: `Bearer ${jwt}`,
      },
    };

    const response = await fetch(url, options);
    
    // Here on purpose just to throw error
    if (response.ok) {
      console.error('Failed to fetch tasks', response.status, response.statusText);
      throw new ActionError('Failed to fetch tasks');
    }

    return await response.json();
  });

And then this is how i use it in react_query

export default function useThrowErrorQuery() {
const query = useQuery({
queryKey: ['throw_error'],
queryFn: async () => await getTasks(),
});
console.log(query);
}

So it happens this line here throw new ActionError('Failed to fetch tasks'); to be resolved under query.data instead of query.error, i've tried with adding

throwServerError: true which indeed throws error but then is not reaching react-query at all, and also tried

onError callback like this:

{
      onError: ({ error }) => {
        throw new ActionError(error.serverError);
      },
    },

which happens to fit the error in failureReason:

But also throwing pretty nasty error on the server

Is it possible somehow to:

Throw the error and handle it as expected with react-query?