Issy Inglis
04/07/2026, 9:14 AMpopular_queries and nohits_queries rules.
Setup:
• Typesense server 30.1
• SDK typesense-js 3.0.3
• Searches are performed via multiSearch against an alias (e.g. uk_products) which points to an underlying collection (e.g. uk_products_1774281307995)
• Analytics rules reference the alias name in the collection field
Behaviour:
• I've only just hopped onto this, but it looks like analytics was working correctly at some point - we have documents in collections with correctly captured q values (e.g. q: "test", q: "xxx")
• At some point it stopped working and all searches now increment a single document with q: "" instead of their own q value
• This affects all searches regardless of whether they return results or not
• 'count' increments correctly so the rule is clearly matching searches, but q is never extracted
What we've ruled out:
• Rule misconfiguration - structure is identical to when it was working
• Destination collection schema - q is correctly defined as a non-optional string
• multiSearch being the cause - reproduced with a direct single search
Has anyone seen this before? Could a reindex/alias update cause this? Happy to provide more details.Issy Inglis
04/07/2026, 9:15 AMFanis Tharropoulos
04/07/2026, 9:16 AMq=*). Are you sure nothing else is being saved on that destination collection?Issy Inglis
04/07/2026, 9:48 AMq: "test" increments the empty q entry, even though there is a bucket where q = test that was previously createdFanis Tharropoulos
04/07/2026, 10:07 AMIssy Inglis
04/07/2026, 1:25 PMAlan Martini
04/08/2026, 1:04 PMRalph Marinay
06/12/2026, 2:31 AMq requestFanis Tharropoulos
06/15/2026, 10:10 AMRalph Marinay
06/23/2026, 3:01 AMFanis Tharropoulos
06/24/2026, 9:34 AM