Maximum update depth exceeded. Involves createNotifyManager in notifyManager.js

[kavitang]

Since we upgraded to react query v5 our app has been throwing a Maximum depth exceeded error continually. This does not seem to be impacting our app, but it is a cause for concern. I'm unable to replicate this in a sandbox environment, and something in our app is triggering this. Please find the error below

Uncaught Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
    at throwIfInfiniteUpdateLoopDetected (react-dom.development.js:26657:11)
    at getRootForUpdatedFiber (react-dom.development.js:7679:3)
    at enqueueConcurrentRenderForLane (react-dom.development.js:7601:10)
    at forceStoreRerender (react-dom.development.js:11914:14)
    at handleStoreChange (react-dom.development.js:11893:7)
    at eval (notifyManager.js:40:9)
    at notifyFn (notifyManager.js:6:5)
    at eval (notifyManager.js:51:13)
    at Array.forEach (<anonymous>)
    at eval (notifyManager.js:50:25)
    at batchNotifyFn (notifyManager.js:9:5)
    at eval (notifyManager.js:49:9)

It seems to be triggered from useBaseQuery

React.useSyncExternalStore(
    React.useCallback(
      (onStoreChange) => {
        const unsubscribe = isRestoring ? () => void 0 : observer.subscribe(notifyManager.batchCalls(onStoreChange)); <----
        observer.updateResult();
        return unsubscribe;
      },
      [observer, isRestoring]
    ),
    () => observer.getCurrentResult(),
    () => observer.getCurrentResult()
  );

This is in a Next js app (v14), running react-query version 5.26.3.

I would really appreciate any hints as to what could be causing this or any leads into potential sources. Our application is large and we use hooks across the app liberally. This issue was not present in v4.

Thanks

[maiconcarraro]

Got a similar sentry report: