Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cache-invalidation-gaps

AntiPattern

Cache Invalidation Gaps

cache-invalidation-gaps

Client-side cache entries don’t get invalidated or revalidated when route/search params change or when updates occur, so suspended/fetched data is stale, queries don’t rerun, and mutations appear to “succeed” without UI updates.

Node Details

Public graph metadata

Updated7/17/2026

Connections

30 linked nodes

MATCHESSolution

Don’t rely on sessionStorage for cross-tab persistence in private mode; use a storage mechanism that matches your required scope (e.g., use localStorage with appropriate handling or another backend/polling approach) and/or implement cross-tab sync via a shared channel such as the Storage API/events when supported.

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

make sure that the form component is only rendered after data is ready — Decouple the data fetching component from the form component. Tension: background refetches will not be reflected. Outcome: if your cache already has stale data when `App` mounts, you'll get that data in your state.

MATCHESSolution

Keep server and client state separated and derive state — It's not a must to initialize `useState` with any value. Tension: The user hasn't made any changes yet. Outcome: meaning "the user hasn't made any changes yet".

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

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

You need to make sure that component that needs that deleted resource is no longer is rendering. Tension: then you set the state that hides that element at the same point where you invalidate the query.

MATCHESSolution

Create a memoized router context object from the app context and call `router.invalidate()` in a `useEffect` when that memoized object changes, so `beforeLoad`/`loader` rerun with the updated data.

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

Set `experimental.dynamicIO` to `false` and enable `experimental.useCache: true`; keep cache behavior via the Route Segment Config (e.g., using `export const dynamic = "force-dynamic"`).

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

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

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

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

Don't store a full URL, just store the necessary information — when going back to the page, validate the data from session storage before building a URL. Tension: not (for instance) a full URL. Outcome: validate the URL before using it.

MATCHESSolution

I'm having SEO issues with a nextJS app where the meta data is being outputted outside of the body tag — I'm using the app router on Next 15.2.3. Tension: Weirdly, if I hard refresh the meta data shows in the head, but when I do a normal refresh it moves down below the script tags at the bottom of the page. Outcome: inside generateBusinessMeta data there is a supabase data fetch.

MATCHESSolution

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

MATCHESSolution

Update state immutably inside the interval (deep-copy or create new arrays/objects for modified shoppers/checkout lines) before calling setState. Optionally remove StrictMode for testing, but the real fix is eliminating nested reference mutation.

MATCHESSolution

Implement `merge` to mutate the existing cache by pushing the new page items into `currentCache` (e.g., `currentCache.data.push(...newItems.data)`), and optionally reset/replace the cache when starting over (e.g., `page === 1`).

MATCHESSolution

You can also use a static field to maintain the cached object. — Separate methods can be exposed to client. Tension: to get the cached instance and to get the new instance based on requirement.

MATCHESSolution

Outcome: cache.clear().

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

Cache Invalidation Gaps - inErrata Knowledge Graph | Inerrata