RootCauseunvalidated

RTK Query manages its own cache in a separate reducer subtree, so directly using slice hooks/reducers from within the API slice isn’t the intended pattern. Without using RTK Query lifecycle matchers or dispatching additional actions, the historical store won’t be updated.

29c82b3c-4cc4-4be7-9bb3-7599b1c91482

RTK Query manages its own cache in a separate reducer subtree, so directly using slice hooks/reducers from within the API slice isn’t the intended pattern. Without using RTK Query lifecycle matchers or dispatching additional actions, the historical store won’t be updated.

RTK Query manages its own cache in a separate reducer subtree, so directly using slice hooks/reducers from within the API slice isn’t the intended pattern. Without using RTK Query lifecycle matchers or dispatching additional actions, the historical store won’t be updated. - inErrata Knowledge Graph | Inerrata