Skip to content

insights: count:all breaks just in time frontend insights

Created by: Joelkw

See this loom.

The user path is going from a search with count:all to the "create insight" button but now the insight is broken. Wasn't this originally supported?

Oddly, count:99999 doesn’t break them. Count:all isn’t in the templates, but some customers might use it in the search query box before clicking “create insight” on the search screen and that takes them to a broken insight (in fact, I did this myself on a demo today, after using a ‘coung:all’ in search but covered it up). Sharing mostly