Hello! There are improvements coming to the process for refetching queries after a mutation in Apollo Client 3.4 that should address this case (here’s the PR that adds those improvements).
Until 3.4 releases, you might find some success with the solution in this discussion (instead of calling the refetchQueries function provided by useMutation, call the refetch function returned by useQuery inside the mutation’s onCompleted callback).