tRPC: Why useQuery() tries to refetch when error occurs while useMutation() doesn't?

I'm using the T3 stack.

test: publicProcedure.input(z.string().min(5)).query(async () => {
        return "hi!";
    }),

test: publicProcedure.input(z.string().min(5)).query(async () => {
        return "hi!";
    }),

const { error } = api.user.test.useQuery("test");

const { error } = api.user.test.useQuery("test");

(it should return a Zod validation error) the client tries to refetch 3 times and then returns the error (4-5 seconds of delay), throughout the process the error is logged by the loggerLink, but the error returned takes a while, but when I switch to useMutation() the error is returned rather instantly, what could be root?

4 Replies

cje•16mo ago

its how react query works

cje•16mo ago

https://tanstack.com/query/v4/docs/react/reference/useQuery

useQuery | TanStack Query Docs

const { data,

cje•16mo ago

if you want to modify the behaviour, you're probably looking for retry or onError

AerysOP•16mo ago

you're right, thanks! 🤟

Gaming

Programming

tRPC: Why useQuery() tries to refetch when error occurs while useMutation() doesn't?

Did you find this page helpful?