Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cache-key-tag-drift

AntiPattern

Cache Key and Tag Drift

cache-key-tag-drift

Cache entries fail to invalidate or hydrate correctly because tag/key construction and placement are inconsistent (e.g., partial prefix keys like todo-list vs my-todo-list, or tags set without immediate use), leading to stale Suspense state and rerenders missing new route/search params.

Node Details

Public graph metadata

Updated7/10/2026

Connections

30 linked nodes

MATCHESSolution

Tension: after logging in, if I navigate to another page, the tokens in my store reset to null.

MATCHESSolution

Leverage React 18's `useSyncExternalStore` — ensure consistent state between SSR and CSR. Tension: client-side state doesn't sync properly with the server-rendered state. Outcome: to ensure consistent state between SSR and CSR.

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

I'm playing around with NextJS app router, and Suspense — In my App router page. Tension: this suspense boundary won't do anything.

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

A fix was applied to TanStack Router to stop using the route as the top-level key, allowing the existing component tree to be reused so the Tabs animation works correctly.

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

Manage the refreshing state more robustly — ensuring it only turns off after all async operations are complete. Tension: remove the arbitrary timeout. Outcome: ensure no state updates occur after the component begins to unmount.

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

use hash-based routing — react + tanstack router + github pages. Tension: The default "browser" routing will exhibit the behaviour you describe.

MATCHESSolution

Add a force reload flag — Next.js App Router API route. Tension: ensure functions aren't reused. Outcome: export const dynamic = 'force-dynamic'; export const revalidate = 0;.

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

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

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

Possible Fix — Given your setup with Expo and `firebase/auth`. Tension: the refresh token mechanism might not be working as expected on your web build. Outcome: Firebase Auth's persistence is configured.

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

Measure the tag container and iteratively adjust from right to left: attempt to keep earlier tags intact, truncate only the last tags as needed (or hide tags that would shrink too much), using refs to read each tag’s scrollWidth/offsetWidth and update visible categories accordingly.

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

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

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

MATCHESSolution

Content-hash dedup against existing entries — before inserting. Tension: For our case (ChromaDB 1845 → Chronicle), 1238/1845 were already present from a prior graph migration. Outcome: Only 607 net-new.

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