How to architect: local resolver re-populates from ssrExchange

[frantisek-heca]

We are running Next Pages Router app, having getServerSideProps.
The first time user visits a product page, the ssrExchange populates correctly the client's cache with ProductQuery.
The consequtive visits of the same product, the getServerSideProps is designed by us to send a fresh ProductQuery in the ssrExchange.
But it's not needed/used, the cached version is already present...

Which was ok until we we wanted to have fresh data from the ProductQuery on each visit.
I tried to use local resolver and return undefined (for the ProductQuery).
Thinking that the ssrExchange will provide the already present ProductQuery.

But somehow it's not working.
When I debug naively the source code...
It seems after returning undefined from a resolver, it does trigger the ssrExchange data correctly.
But then it tries to updateCacheWithResult and inside it does _query (queryResult) the same ProductQuery and the resolver is triggered again and returns undefined and it loops in this pattern.

Any ideas, advice, please?
I cannot play with (work with) ssrExchange cache from resolvers, right?