Changing `retryDelay` is ignored for query about query HOT 2 CLOSED

the options do update on the query, but not on the retry. Let me explain:

when a query starts to run, we create an internal retryer and pass options from the query to it:

Then, that retryer takes those options, returns a promise and will resolve or reject it once the whole process of fetching is complete. This takes retries, network availability etc. into account. Fore example, the query might go into paused state in between and continue with retries later.

So the retryer will see the options from the time it was created (=when the fetch started). Usually, this is what you want because the retry process is opaque. The promise will resolve or reject eventually, and then, when a refetch occurs (which is different from a retry), the new values will be respected.

We could make those values reactive in between retries, but I think that'll open up a can of worms. What if you change retries from 5 to 2 while you are at the 3rd retry? What if you change networkMode to 'always' while the query is paused because you have no network connection? It's the safer approach to just trigger the whole process (fetch + retries) with a given set of options from creation time until it is finished. It's a bit how closures work with react functions, too.

Both retry and retryDelay can be a function, so you can define them as a function and use a ref to read the latest value inside of it if you really want.

from query.

I had the same issue trying to update a variable inside useQuerywhitout updating the queryKey

useQuery will only update the variables within it if the queryKey is changed. As it stands, even changing the retryDelay the query will not have its values ​​updated, since the queryKey has not changed
If you change line 12 to this one you will see that the problem has been solved

    queryKey: ['test', retryDelay],

refetchInterval is used to revalidate the query, so it will only work if it is successful.

I think that it happens because of the caching in react-query. The function will not update is own values if the key doesn't change, it will only update the data.

Maybe I'm making a mistake trying to prove you my point (I've heard it while a go, so that is the reason that I know it), but maybe the useQuery component will only trigger the useEffect and rerender it state when some of the options in queryKey, queryFn changes.

https://github.com/TanStack/query/blob/main/packages/react-query/src/useBaseQuery.ts#L91

from query.