useLazyQuery run after component rerender

[pronovaso]

Hi all.

I switch to new version of Apollo client. Actually v 3.3.6.

I use useLazyQuery in component with useQuery and useMutation. If I clicked on button,which open confirm window,then I call useLazyQuery function called load({variables:{id}}), query runs and give me a data. Thats right.But after run some mutation and query for new data from useQuery, than useLazyQuery runs again with same id. But load function is on handleClick, which not fire and this id is only from this handleClick.

And I dont know why. One difference is, new inMemoryCache. When I use this from package apollo-inmemory cache and not from @apollo/client than everything is allright.

Can you someone explain me, what I doing wrong or maybe bug in InMemoryCache?

Thans and sorry for my english :-)

[hyperxpizza]

Similar issue here. UseLazyQuery seems to send a request to the server everytime my component re-renders.

"@apollo/client": "^3.3.6",
"@apollo/react-hooks": "^3.1.3",

[aub]

Same here

[pedrochiossi]

Also having this problem, fired lazyQuery, after it finishes, other queries run in sequence, some are even using old variables from previous calls. Seems to be a problem in cache handling, it works if I use the "no-cache" fetchPolicy.

[pronovaso]

Also having this problem, fired lazyQuery, after it finishes, other queries run in sequence, some are even using old variables from previous calls. Seems to be a problem in cache handling, it works if I use the "no-cache" fetchPolicy.

Yes same here. In my case, if I change fetchPolicy to "no-cache" and query runs, I have same old value.
For example....I create a new request in form and then run fetch some query, network request will place, but in menu, where should change number from request, I have same old number.

[dlindahl]

I believe I am experiencing this same issue. I have a useLazyQuery with a fetch policy of network-only that, once it has been explicitly executed once by a user interaction, is making additional network requests over the wire whenever the component re-renders, even though the execute function, nor the refetch function, have been explicitly called.

After poking around a bit in useBaseQuery, it looks like a forceUpdate is getting triggered with an increase in the tick value even though none of the lazy query's variables are changing in the host component. I have confirmed this behavior by hardcoding the query variable values to primitives so that they always have referential equality. In that scenario, I would never expect a lazy query to re-execute unless explicitly asked to via the execute function or refetch.

[aquelehugo]

I think we can use nextFetchPolicy: 'cache-first', as a workaround, just so network requests are avoided. But it is a bug a for sure

[limekiln]

I am experiencing this as well, although, for some reason, only if the previous intended call of the lazy query returns an error. If the query resolves corretly and returns data, no follow up requests are made.

[robinjhuang]

Also having the same issue. useLazyQuery re-runs the query on component re-render.

[andremoah]

This issue is also happening to me and it seems a bug since the documentation states "The useLazyQuery hook is perfect for executing queries in response to events other than component rendering."

I have tried every type of fetchPolicy without any success (even though it does not feel right because it still creates a new network request), the requests are always re-executed on component render resulting in data going back to undefined and then to the new request request (onCompleted is always re-executed as well).

This totally invalidates the objective and usage of useLazyQuery.

[assimovt]

same issue here