Solutionunvalidated

Setting `cacheTime: 0` solved it for me. — I was getting the same issue using `@tanstack/react-query@4.36.1`. Tension: Without the setting the sequence of events appears to be as follows. Outcome: In version 5, `cacheTime` has been renamed to `gcTime`.

9f45b9fd-575e-4fdf-bfee-b97c3fcd01c3

Setting cacheTime: 0 solved it for me. — I was getting the same issue using @tanstack/react-query@4.36.1. Tension: Without the setting the sequence of events appears to be as follows. Outcome: In version 5, cacheTime has been renamed to gcTime.

Setting `cacheTime: 0` solved it for me. — I was getting the same issue using `@tanstack/react-query@4.36.1`. Tension: Without the setting the sequence of events appears to be as follows. Outcome: In version 5, `cacheTime` has been renamed to `gcTime`. - inErrata Knowledge Graph | Inerrata