Dispatching initiate() function resolves with a status of pending

[npfitz]

I'm currently running into a situation where I call initiate() on an endpoint that currently has a request in flight (due to tag invalidation), but the value I'm returned is the previously cached entry, alone with some metadata such as isLoading: true and status: pending. For example:

await dispatch(cardApi.endpoints.getCard.initiate({id}, {forceRefetch:true})

returns an object like

{
    "status": "pending",
    "endpointName": "getCard",
    "requestId": "JOhITYA33zsbG75F0IuRo",
    "originalArgs": {
        "id": 18
    },
    "startedTimeStamp": 1732104749367,
    "data": {
        /* Cached data entry */
    },
    "fulfilledTimeStamp": 1732104744906,
    "isUninitialized": false,
    "isLoading": true,
    "isSuccess": false,
    "isError": false
}

For some reason, even though there is an in flight request we are resolving the promise immediately with cached data. However, if I delete the cache entry before my call to initiate, awaiting initiate will work as expected. So my current work around is to dispatch cardApi.internalActions.removeQueryResult before calling initiate.

Is this expected behavior? Is there any way to access the promise of the in flight response above? Thanks in advance.

Edit:
This is using @reduxjs/toolkit@2.2.5

[EskiMojo14]

I suspect you should be able to use getRunningQueryThunk to get the promise from the request currently in flight.

[npfitz]

Interesting! I'll give that a try and report back. Thanks @EskiMojo14

[npfitz]

@EskiMojo14 It seems to be returning undefined. When I try dispatching getRunningQueriesThunk I get back an empty array

[phryneas]

That sounds very suspicious. Could you try to create a reproduction of that?

[npfitz]

@phryneas Absolutely! Do you mean my original issue, or getRunningQueriesThunk returning an empty array? Is there any chance there is a code sandbox available with a dummy app? haha

[phryneas]

Ideally both, but I'm more intrigued about getRunningQueriesThunk returning an empty array - if we can see that, we can probably answer both questions.

You could e.g. start with https://codesandbox.io/p/sandbox/github/reduxjs/redux-toolkit/tree/master/examples/query/react/basic but please update the RTK versions, that's unfortunately quite outdated

[npfitz]

@phryneas good news! I set up a code sandbox that illustrates my issue, and I was using @reduxjs/toolkit@2.2.5 like we are in our environment. I was able to reproduce it, but in the sandbox I updated to 2.3.0 and the issue appears to be resolved. I'll try updating on our end to see if that helps!

Sandbox is here if you're curious

[markerikson]

@npfitz that seems surprising, because nothing in 2.3.0 should have changed any of that behavior:

• https://github.com/reduxjs/redux-toolkit/releases/tag/v2.3.0

[npfitz]

@markerikson It seems that 2.2.8 is where the issue was fixed, based on what I'm seeing in the sandbox by changing the version numbers up and down

[markerikson]

Ah, okay, that might be related to the changes in #4651

[npfitz]

I think we can close this issue then. Thanks all for the help in diagnosing!