RTK Query refetchOnFocus not triggering after setupListeners — what else controls it?

To enable refetchOnFocus, you must both call setupListeners(store.dispatch) and opt-in via the refetchOnFocus flag. If setupListeners is active but no network request occurs, the most common cause is that the query hook is not currently mounted in the component tree, or the specific configuration level has disabled the behavior.

Configuration Hierarchy and Precedence

RTK Query follows a "most specific wins" hierarchy for the refetchOnFocus setting. If you have conflicting settings, they resolve in this order:

1. Hook Level: Options passed directly to the hook call (e.g., useGetUsersQuery(undefined, { refetchOnFocus: false })) take the highest priority.
2. Endpoint Level: Settings defined within the endpoints object in createApi.
3. Global Level: The refetchOnFocus setting in the createApi configuration object.

If you enable it globally but disable it on a specific endpoint, that endpoint will not refetch on focus.

Cache Interaction and Subscription State

A window focus event does not automatically force a network request for every single cached item. Two conditions must be met for a refetch to trigger:

• Active Subscription: The query must be "active" (i.e., the hook is currently mounted in a component). RTK Query will not refetch data for components that are not currently on screen.
• Opt-in Status: The refetchOnFocus flag must be true for that specific query.

Unlike refetchOnReconnect, which often focuses on restoring connectivity, refetchOnFocus is designed to refresh the UI. If the flag is true and the hook is mounted, RTK Query will trigger a refetch regardless of whether the cache entry is still within its keepUnusedDataFor lifetime.

Verification via Redux DevTools

You can verify if the listener is working independently of the network request by monitoring the Redux DevTools action log. When the window regains focus, look for the following action:

api/executeMutation or api/executeQuery (triggered by the internal refetchOnFocus logic)

If you see the focus-related action dispatched but no network request follows, the issue is likely that the query is not currently subscribed (mounted) or the endpoint-level flag is false.

Diagnostic Check

Are you running the application inside an iframe or a specialized webview? Window focus events may not bubble correctly in these environments, preventing setupListeners from detecting the event.