nextFetchPolicy doesn't work as expected.

Preface: My understanding from the docs has been that while using useQuery, the first execution takes place as specified by fetch-policy. All subsequent executions of the query follow nextFetchPolicy(If Specified).

Intended outcome: I set the fetchPolicy to cache-first and nextFetchPolicy to network-only expecting that a network request will be made on every execution after the first.

Actual Outcome: But the same isn’t replicating. On subsequent executions, data is getting read from cache and no network-request is made.

How to reproduce the issue: Here is a codesandbox to check the same Link.

Versions version : 3.4.8

Am I misunderstanding nextFetchPolicy or is this a bug?

[dylanwulf]

fetchPolicy is used every time the component mounts. nextFetchPolicy is used for every query execution after the component mounts. When you unmount and remount the component, it resets to fetchPolicy. Unfortunately it isn’t super clear in the docs exactly what “first execution” means.

[dylanwulf]

@santialbo “changing the variables” and “calling refetch” are not the only things that could cause a query execution. I believe if some related data in the cache gets updated, that is another scenario where the query would get re-executed.