NRather than refetch you should use invalidate from trpc.useContext https://trpc.io/docs/reactjs/usecontext
useContext is a hook that gives you access to helpers that let you manage the cached data of the queries you execute via @trpc/react-query. These helpers are actually thin wrappers around @tanstack/react-query's queryClient methods. If you want more in-depth information about options and usage patterns for useContext helpers than what we provide...
NRefetch should work, but invalidate is the correct way to do this in RQ
NCould you share some small reproduction in a stack blitz? Might be something weird going on
NOh yes that makes sense, there’s the something weird!
NOften in these situations the simplest solution is to instead reload the page. It’s a fairly fundamental change to the account state which is invisible to the query
NStructurally speaking it would be better to have a dedicated page to complete the invite flow and then redirect onward to this one