Should you avoid nesting QueryClient?

We have a large enterprise app with multiple teams working on features that use RQ. We're in the process of introducing a

QueryClientProvider

QueryClientProvider

at the app's root level which would create nested clients. Is this something to avoid? I assume calls like

queryClient.invalidateQueries

queryClient.invalidateQueries

will be limited to their closest provider, but I could see this being confusing in a large codebase.