`skipToken` is passed into my `infiniteQuery` as a `queryArg`

[markerikson]

Discussed in #5027

^{Originally posted by soggybeef July 4, 2025}
Language: Typescript
Version: "@reduxjs/toolkit": "^2.3.0",

I was trying to conditionally run an infinite query to prevent the first request from being made upon mounting of the component. The args will be taken from router which is from next/router

I have the args for queryArg as shouldSkip ? skipToken : args. But when shouldSkip === true and skipToken is passed in, the first request is still being made, and this is what i got from my console logs when forming the query in the services page where the endpoint is defined:

Since the logic of forming my queryParams doesn't and shouldn't take into account the skipToken, the request is still being sent in to fetch data that i don't want to fetch. This data is returned, but not returned or populated to my parent component. But I see it under the Responses in my Network Requests.

Would love any tips and corrections on how I can better handle the skipToken in my infiniteQuery, thank you!

EDIT: I see similar behavior when using skip: shouldSkip as part of the second argument in my useInfiniteQuery; the original args that I had became the queryArgs and the request is sent and returned, but not poulated.

[markerikson]

@soggybeef that sounds very odd. Could you provide a CodeSandbox or repo that shows this happening?

[soggybeef]

I'll try to set up the CodeSandbox soon but, basically now i have this code block in my frontend component. I keep getting the error in the below screenshot in my console logs in the Developer Tools. The isLoading boolean is dependent on router.isReady, so that will cause the child component to render a loading wheel conditionally, which works fine in accordance to my boolean.

const {
    data,
    fetchNextPage,
    hasNextPage,
    isFetchingNextPage,
  } = useGetPeoplefiniteQuery(isLoading ? skipToken : filters, {
    pollingInterval: API_REFETCH_DELAY,
  });