Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cluster-62

ClusterConcept

Cache Invalidation Mismatch

cluster-62

Cache keys and invalidation signals get wired to the wrong shape (undefined inputs, unbound query client methods, tag scopes, or incorrect parameter/header interfaces), so queries either never run or re-fetch unexpectedly after mutations.

Node Details

Public graph metadata

Updated6/9/2026

PageRank0.0002

Connections

43 linked nodes

INSTANCE_OFProblem

Query callers must remember to destructure and call refetch manually after a mutation

INSTANCE_OFProblem

Query code and mutation code are unnecessarily coupled

INSTANCE_OFProblem

I want to keep these queries separate, but in the UI I want to consume them as one combined object — I have two separate queries using `@tanstack/angular-query`. Tension: I can't figure out how to combine the results like this. Outcome: Is there a built-in way in TanStack Query for Angular to derive/merge the results of two queries into one object.

INSTANCE_OFProblem

previous in-flight requests are not cancelled by `injectQuery` — Angular 18 with TanStack Angular Query. Outcome: I searched for a possible workaround, but did not find any.

INSTANCE_OFProblem

useQuery request takes about a minute to download content and returns no data

INSTANCE_OFProblem

Whether React 19's new `use` hooks will replace the functionality provided by TanStack Query (TanStack Query library).

INSTANCE_OFProblem

When using react-query's useQuery, attempts to access props like data.role are undefined even though the fetched response contains role information. Logs show the top-level data object has only user and message, while role is nested under user.

INSTANCE_OFProblem

Error: Invalid AST Node: {}. — queryFn: async () => graphqlRequestClient.request(getWineTypesDocument). Tension: some typescript related errors around the graphql query itself, which may or may not be related. Outcome: I was able to solve this error by removing the `graphql` function that was wrapping the query.

INSTANCE_OFProblem

it keeps converting the multi-valued search param 'fruits' (string[]) to comma separator — I am using React-Router `useNavigate()` to navigate to another webpage after selecting the column filters. Tension: making my query string look like this instead - `"type=fruit&filter=sour,sweet"` instead of using ampersand separator e.g. `"filter=sour&filter=sweet"`. Outcome: I tried many methods such as conversion and replace but it didnt work.

INSTANCE_OFProblem

Type '(title: any) => Promise<AxiosResponse<any, any>>' has no properties in common with type 'UseMutationOptions<unknown, Error, void, unknown>' — The problem occured at line 13: `async (title) => await axios.post("/api/posts/addPost", { title });`. Tension: The current V5 React-Query useMutation hook consumes an options object, not an asynchronous function. Outcome: Update to pass the fetching function as the mutation's `mutationFn` property.

INSTANCE_OFProblem

would prefer to not call `convertDataToTasks` inline in JSX when rendering — React-Query to cache the data you want to render from. Tension: especially caching.

INSTANCE_OFProblem

I'm trying to understand the difference between the initialData and placeholderData options in the React Query v5 useQuery hook. — in the React Query v5 useQuery hook. Tension: I'm unclear on when to use each of these options. Outcome: What are the specific scenarios or use cases where `initialData` or `placeholderData` would be more appropriate?

INSTANCE_OFProblem

The user attempted to call `trpc.*.useQuery` inside a `useEffect` and then set state from `clientQuery.data`, which is an incorrect hook usage pattern. They were concerned that `useQuery` (a hook) cannot be used inside another hook.

INSTANCE_OFProblem

I want that the new data will appear immediately — Querying the blogPostData from the server using its id. Outcome: The blog post ID must be part of the key.

INSTANCE_OFProblem

No overload matches this call. — using "useInfiniteQuery" with React. Outcome: Try to add `initialPageParam: 1,`.

INSTANCE_OFProblem

created infinite loops if setQueryData was called from within onSuccess — from the official documentation. Tension: This was confusing to many. Outcome: onSuccess is no longer called from setQueryData.

INSTANCE_OFProblem

These Todo items can be "completed", which triggers a mutation call to the back-end but optimistically updates (via `setQueryData`) the individual item. Tension: Making these optimistic updates across multiple lists of Todos is fairly complex and feels inefficient. Outcome: then any child components that need to render that data can just get the Todo object from the react-query cache.

INSTANCE_OFProblem

Types of property 'isSuccess' are incompatible. — Argument of type 'UseQueryResult' is not assignable to parameter of type 'QueryResult'. Tension: Type 'QueryObserverRefetchErrorResult' is not assignable to type '{ isSuccess: true; isPending: false; isError: false; data: { transactions: Transaction[]; }; }'.

INSTANCE_OFProblem

I have the following code. — queryFn: () => { makeRequest.get("/posts").then((res) => { return res.data; }) }. Outcome: return res.data.

INSTANCE_OFProblem

TanStack useMutation does not cause useQuery to show the newly added product

INSTANCE_OFProblem

mutateSale({ customerId: customer.id, salesDetail: orderList, }). Tension: I've read documentation and it says that `mutate` receives the first parameter as variables. Outcome: get rid of the angle brackets `<>` and use type inference.

INSTANCE_OFProblem

Cannot create property 'exact' on string 'todos' TypeError — const queryData = queryClient.getQueryData('todos'). Outcome: The error Im getting noe is: `Cannot create property 'exact' on string 'todos' TypeError: Cannot create property 'exact' on string 'todos'`.

INSTANCE_OFProblem

vue-query hooks can only be used inside setup() function or functions that support injection context. — Whenever I try to call useQuery inside a function. Tension: I need to query an API as a side-effect of an action. Outcome: I concluded that vue-query can only be called from setup function only.

INSTANCE_OFProblem

Now, I want to make the Next button its own component and pass the Infinite Query variables to it as a prop. Tension: Typescript automatically assumes the types of the Infinite Query variables like `data`, `error`, etc. using the types provided by the library.

INSTANCE_OFProblem

Bad argument type. Starting with v5, only the "Object" form is allowed when calling query related functions. — useQuery(['users'], async() => {. Tension: Please use the error stack to find the culprit call.

INSTANCE_OFProblem

invalidateQueries({ queryKey: ['profile'] }); — onSuccess: () => {. Tension: the profile request (which returns user and favorites). Outcome: This will work:.

INSTANCE_OFProblem

It contains both RESTAPIs and GraphQL queries — our project is very bad. Tension: is it good to have both react-query and apollo-client on the FE app? Outcome: or vice versa, can I use react-query for GraphQL queries like for REST APIs?

INSTANCE_OFProblem

useQuery({ queryKey: ["dates"], queryFn: getDates, });. Tension: the initial value is only set on the first render.

INSTANCE_OFProblem

TS2339: Property 'pageParam' does not exist on type '{ queryKey: QueryKey; signal: AbortSignal; meta: Record<string, unknown> | undefined; }' — const queryFn: QueryFunction<Awaited<ReturnType>> = ({pageParam}) =>. Tension: i have this code. in v5 tanstack i get problem with. in v4 is not have this problem.

INSTANCE_OFProblem

useQuery data is inferred as any[] | AxiosResponse when a default empty array is assigned

INSTANCE_OFProblem

useQuery returns undefined because no queryKey is passed

INSTANCE_OFProblem

since `UserResponseDto[]` does not extend `UserResponseDto` — export const useAllUsers = ( select?: (data: UserResponseDto[]) => T ) => useQuery({. Tension: so in no case could that be `UserResponseDto[]`. Outcome: you could do ``, to allow `select` to return any type.

INSTANCE_OFProblem

Converting a pull request to draft does not work in private repositories

INSTANCE_OFProblem

In a Next.js App Router page, the user needs the raw query parameters string (e.g., "param1=lorem&param2=ipsum...") inside a component.

INSTANCE_OFProblem

How to take RTK Query endpoint results, persist them as historical data for graphing, and also keep the normal RTK Query caching behavior. The user wants to “intercept” fulfilled query results inside the RTK Query flow rather than using component hooks.

INSTANCE_OFProblem

In RTK Query, after performing a mutation (e.g., login), the developer cannot easily select/read the data that the mutation stored in the cache from another component/hook instance.

INSTANCE_OFProblem

The user gets TypeScript/logic issues when trying to return Firestore data formatted for an RTK Query `createEntityAdapter`, especially while attempting to use both `queryFn` and `transformResponse`. The endpoint also fails because `queryFn`/return shape expectations conflict with how `transformResponse` is meant to operate.

INSTANCE_OFProblem

When following the RTK Query example for mutations without React hooks, it’s unclear what query key/argument should be passed to `api.util.updateQueryData` to optimistically update the cache for the last `getUsers` query. The snippet appears inconsistent about using `id` vs `count`.

INSTANCE_OFProblem

export const { useGetPokemonByNameQuery } = pokemonApi. Tension: This is likely not portable. Outcome: A type annotation is necessary.ts(2742).

INSTANCE_OFProblem

RTK Query hook export triggers ts(2742): inferred type cannot be named without a reference to buildHooks

INSTANCE_OFProblem

RTK Query mutation query receives the wrong argument shape for updateUser

INSTANCE_OFProblem

In an RTK Query endpoint, the request should include query parameters only when their values are not null, but optional params are being added unconditionally or require repetitive manual checks.

INSTANCE_OFProblem

Tension: PrepareHeaders Error. Outcome: Move the `prepareHeaders` property into `fetchBaseQuery`.

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

© 2026 Inerrata

Cache Invalidation Mismatch - inErrata Knowledge Graph | Inerrata