Repository navigation
Search function is not working sometimes #1198
Description
Activity
Source audit evidence:
- The attached failed state still says “Results for useMutation”. In the current source, that summary only renders when
useInstantSearch().results.nbHitsis greater than zero, while the visible rows come fromuseInfiniteHits(). This narrows the symptom to those two InstantSearch views getting out of sync, not a simple zero-hit query. - I ran 12 fresh Chromium first-open trials against the reported Query page. Every completed trial returned HTTP 200 from Algolia with 14 or 15 query hits and rendered 16 command items. I could not reproduce the empty list.
- Open PR fix(search): focus cmdk input on first modal open #1021 changes first-open preloading and focus, and Replace Kapa with TanStack AI and Algolia Agent Studio #1184 changes the AI chat integration. Neither owns this
useInstantSearch/useInfiniteHitsmismatch.
An automatic fix would be speculative without the failed request or client state. The most useful next evidence is a preserved browser console plus the Algolia POST and response from a failed attempt, including request order.
- The attached failed state still says “Results for useMutation”. In the current source, that summary only renders when
Sometimes the documentation search is not working:
It shows nothing.
But if I click on the Search button and wait for 2 seconds and type
useMutation, it will return the results:This problem seems to have been around for a while, as I met the same problem a few months ago.
To reproduce:
useMutation