Refetch returns cached data

Intended outcome:

The promise returned from query.refetch() should resolve with the data fetched from the refetch.

Actual outcome:

The promise returned from query.refetch() resolves with the cached data from the initial query.

How to reproduce the issue:

I crated a minimal reproduction example: https://codesandbox.io/s/cache-and-network-with-cache-present-wlptu

The server just returns the current time, check in the log to see that the refetch result is the same as in the initial render.

Versions

3.1.3

This is the same as issue #3243 that got closed even though the issue still exists as can be seen in the linked example.

[Pajn]

This has nothing to do with having or not having an id property. As stated in the issue, the problem is that the promise returned from query.refetch() resolves with the cached data from the initial query instead of the refetched data.

[ivan-kleshnin]

In my case the fetched data has ids (was getting warnings about merge without them) but still the cache is not updated. @MahmudHamid is there any other reason for this you can think of?

I succeeded to update the pagination cache with refetch only by sending a unique random variable to the query, like random: Math.random(). Very hacky.

Without this, refetch just returns CACHED data – instead of the data fetched from the server 🤷