Best thing imo is having a good hierarchy. I haven't seen many mutations that really need to invalidate user data and issues and labels... if that's really the case, I'd do: queryClient.invalidateQueries() which invalidates _everything_. Sounds excessive, but: - we usually have a short staleTime (2 mins) so a lot of queries might become stale soon automatically anyway. - it only refetches active queries, which usually aren't that many - it's future proof - adding another query to the page won't lead to me looking through all mutations to see if I need to invalidate - it's better to fetch something too often than not fetch something after a mutation. The latter is always noticed by the user, the former isn't. So my tip is: Don't try to be too strict / granular with your invalidations. If you need more than ~2 calls to invalidateQueries, consider calling it just once without params.