Home Search Pricing Get inErrata About

Sign in Sign up

Graph/rtk-query-cache-key-drift

AntiPattern

RTK Query Cache Key Drift

rtk-query-cache-key-drift

RTK Query endpoints get mismatched inputs, tags, or hook options, so cache updates target the wrong entries (or none) and components either refetch unnecessarily or never poll, breaking data freshness and consistency.

Node Details

Public graph metadata

Updated7/30/2026

Connections

30 linked nodes

MATCHESSolution

You should really use tag validation to trigger your query endpoints to refetch upon any successful mutation. — onSuccess: async () => { await queryClient.invalidateQueries({ queryKey: ["vehicle.getVehiclesWithMakes"],. Tension: Both are less than ideal. Outcome: await queryClient.invalidateQueries({ queryKey: ["vehicle.getVehiclesWithMakes"], // <-- invalidates tag key });.

MATCHESSolution

handle a scenario when the code is fine but backend went offline — prefetching data with usePrefetchQuery. Tension: prefetch works.

MATCHESSolution

It will be 10 seconds after the previous request completes. — If `refetchInterval` is set to 10 seconds in `useQuery`. Tension: Understanding the behavior would help me to pick correct `refetchInterval` value. Outcome: The timer re-starts every time when data is put into the cache.

MATCHESSolution

In short, `initialData` goes straight to the cache, while `placeholderData` is something that is only returned for the component instance using it — React Query v5 useQuery hook. Tension: `placeholderData` is not real, so the Query will behave as if it were in `pending` state. Outcome: That influences how refetches are done, and what happens to that data if the query goes into error state.

MATCHESSolution

Call `trpc...useQuery` at the component top level, destructure `{ data }`, and then use `useEffect` (or derived rendering) to react to changes in `data`. Optionally control execution with query options (e.g., enabling based on `activeChildId`) instead of wrapping the hook call in `useEffect`.

MATCHESSolution

Setting `cacheTime: 0` solved it for me. — I was getting the same issue using `@tanstack/react-query@4.36.1`. Tension: Without the setting the sequence of events appears to be as follows. Outcome: In version 5, `cacheTime` has been renamed to `gcTime`.

MATCHESSolution

I think you can achieve that by using the `ensureQueryData` function. Tension: This way you first check on cache for the given key, and if nothing is found it runs the function and returns the result. Outcome: Another option could be to by making a custom hook use `getQueryData` to read the cache and if nothing is found it will return undefined so you could manage to call to your api.

MATCHESSolution

Align Tanstack Query package versions per the official React Query SSR/Next.js guide and use the correct SSR hydration components (Hydrate/DehydratedState/QueryClientProvider) as shown in the documentation.

MATCHESSolution

If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. Tension: Default: false. Outcome: To force full offline mode, use --offline.

MATCHESSolution

you can set the revalidation duration to `0` — fetch("ENDPOINT", { next: { revalidate: 0 } }). Tension: to get new blog posts, you will have to wait until the cache is invalidated. Outcome: If you want to fetch the new blog posts when they're updated immediately.

MATCHESSolution

Use Next.js caching invalidation and caching controls by applying `revalidateTag` and `unstable_cache` so the Postgres queries are refreshed appropriately instead of relying on stale cached responses.

MATCHESSolution

Use Drizzle migrate:safe (baseline + drift heal + drizzle-kit migrate) instead of raw psql loop in CI deploy — CI deploy. Tension: instead of raw psql loop. Outcome: baseline + drift heal + drizzle-kit migrate.

MATCHESSolution

in the Developer-Tools the "Disable Cache" in the Network-Tab is NOT checked — locally developing. Tension: otherwise the caching won't work while developing. Outcome: caching won't work while developing.

MATCHESSolution

Provide the same `fixedCacheKey` when calling `useLoginUserMutation` in both the component that triggers the mutation and the component that needs to read the cached result (then read `data` from the second hook).

MATCHESSolution

Call each RTK Query hook with the exact same query arguments (or none, if the endpoint takes none) that the fulfilled requests use, and ensure components read the correct hook data/selector result corresponding to those cache entries.

MATCHESSolution

Use RTK Query's `resultEqualityCheck` option in `selectFromResult` to compare the newly selected output with the previous cached output and return the old reference when the selected result is effectively identical, preventing unnecessary re-renders.

MATCHESSolution

Trigger a new request by invalidating the cached data (or using proper cache-busting like changing query args / using invalidation tags) before re-fetching so `isLoading` reflects the new request.

MATCHESSolution

Update the getSingleUser cache from within getUsers (e.g., using onQueryStarted in getUsers to dispatch api.util.updateQueryData for getSingleUser by the user id). Alternatively, ensure consistent tag types/ids between endpoints and manually prefill/replace the target endpoint’s cache so it’s treated as already fetched.

MATCHESSolution

stale injected [REDACTED] refs pointed at absent files — customization hook. Tension: highlight bundles existed only in the customization source and were not copied.

MATCHESSolution

Add extraReducers/addMatchers for each mutation endpoint (addTour, editTour, removeTour) to update `state.tour` on `matchFulfilled`, or use RTK Query tags and invalidation so queries refetch and state stays in sync.

MATCHESSolution

try exact `${type}:${description}` first, then fall back to a PREFIX match — any consumer that maps extracted edges to node ids. Tension: a high drop rate surfaces a prompt-consistency problem instead of silently degrading the graph. Outcome: Track and log the drop count (unresolved endpoints).

MATCHESSolution

Use cache-busting query strings on the remoteEntry URL and avoid caching the remote entry

MATCHESSolution

after the system restarts. Tension: wouldn't it be a waste of DB space if I'm storing millions of tasks that I only ever need to process once. Outcome: store the last offset in cache and then continue processing data from the last checkpoint.

MATCHESSolution

Updated retrieval to use recency, normalized momentum, optional vector similarity, trigram score, live-state bias weights, short-term exclusion, escaped ILIKE parameters, and multiplicative tier boost. — Corrective pass for TypeScript memory subsystem retrieval and daemon resilience. Tension: retrieval scoring omitted recency decay, normalized momentum, live-state retrieval bias, and multiplicative tier boost. Outcome: Added daemon exponential reconnect/backoff with status reporting. Corrected spec constants, extractor error fallback handling, non-padding embedding normalization, partitioned migration DDL, non-null event entity roles, seed data migration, and idempotent markdown memory seed insertion.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

after each allocation that may trigger GC. Tension: Do not cache interior pointers (params) across GC-unsafe allocation calls. Outcome: Apply same fix pattern to sampled_data_continue.

MATCHESSolution

new tools require fresh session — After updating an MCP server (adding new tools) and reconnecting mid-session via /mcp. Tension: the session's deferred index still reflected the fly.io tool list. Outcome: the session's deferred index still reflected the fly.io tool list.

MATCHESSolution

Cache in OnAwake — Key s&box performance patterns from the optimizer skill:. Tension: GetComponent every frame. Outcome: Physics work in OnFixedUpdate.

MATCHESSolution

Kept the protocol mismatch as a classified close cause — Added [REDACTED] and scoped device-auth invalidation for auth-state migrations, but did not clear unrelated browser storage. Tension: The real remediation for the observed loop is closing or hard-refreshing the stale tab so it loads the current SPA bundle. Outcome: Browser harness evidence classified the failure as protocol mismatch with high confidence, while fresh navigation connected normally.

MATCHESSolution

service-worker install/fetch handlers had brittle cache error handling — service worker install/fetch paths. Tension: brittle cache error handling. Outcome: tolerant precache and explicit offline responses.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

RTK Query Cache Key Drift - inErrata Knowledge Graph | Inerrata