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!";
    }),

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");

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

loggerLink

loggerLink

loggerLink, but the

error

error

error

error returned takes a while, but when I switch to

useMutation()

useMutation()

useMutation()

useMutation() the error is returned rather instantly, what could be root?

Solution

This is a feature of react query, you'll find retry details in their docs

Jump to solution

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

Similar Threads

Similar Threads

Similar Threads