You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use the timeToLive setting, entities seem to be expiring in the cache — but, after expiring, even though the query is correctly firing a network call again the next time it is requested (although, would have preferred it to automatically fire again as soon as the cache expires), the data object received is undefined
This is super strange, because I can see the request being fired and a response being returned, but nothing is received by Apollo — it's as if the new response isn't being written to the cache? Perhaps that query is stuck with an old cache key?
The text was updated successfully, but these errors were encountered:
Thanks for the report! So a query expires via TTL, it goes to network to get the data again, but it never returns that data? Is there a repro I could look into?
@danReynolds Yeah that's exactly what's happening — I see the network request, and const { data } = useQuery(..) is undefined, even though the request just came through. Disabling TTL again fixes it
Unfortunately our repo is private but I tried to reproduce the behaviour here, and can get similar behaviour:
When we use the
timeToLive
setting, entities seem to be expiring in the cache — but, after expiring, even though the query is correctly firing a network call again the next time it is requested (although, would have preferred it to automatically fire again as soon as the cache expires), thedata
object received isundefined
This is super strange, because I can see the request being fired and a response being returned, but nothing is received by Apollo — it's as if the new response isn't being written to the cache? Perhaps that query is stuck with an old cache key?
The text was updated successfully, but these errors were encountered: