Queries running slowly
Ticketclosed
Grisedale Search & Selection: documents · Queries running slowly
Broad queries taking excessive time, especially searches across six months of data. Root cause identified as unoptimised index for large date-range queries. Issue escalated to engineering for composite index.
What happened
What this says
Current to 11 Oct 26Broad queries taking excessive time, especially searches across six months of data. Root cause identified as unoptimised index for large date-range queries. Issue escalated to engineering for composite index.
Problem: Lauren reported queries running slowly, especially broad searches across six months of interactions by client type. Handling: Bethan identified that broad date-range queries were performing full table scans without index optimisation. She escalated to engineering team with recommendation for a composite index on client_type and date fields. Watch: Ticket shows escalation but no confirmation of resolution. Need to verify whether index optimisation was completed and whether query performance improved for the customer.
Details
Updated 9 Oct 26Trail
created · Lauren Pilkington 15 May 2026 09:27Hi, I've been noticing that when we run queries in the brain, they seem to take quite a long time to come back - especially if we're searching across a lot of data. Is there something we can do to speed it up, or is it just a case of waiting for it to process?- public_reply · Bethan Lister 15 May 2026 20:26Thanks for flagging this. Slow query performance usually means we need to look at what's being searched and how the data is structured. Can you give me an example of a query that's slow - what are you searching for and roughly how many records does it need to scan?
- public_reply · Lauren Pilkington 19 May 2026 10:58Hi Bethan, for example I ran a search for all interactions with a particular client type across the last six months, and it took ages. I'd expect that to be quicker given the dataset size.
- public_reply · Bethan Lister 19 May 2026 14:09That kind of broad query across six months of data can be slow depending on how it's indexed. The good news is we can optimise this. I'm going to escalate to the engineering team to review your index structure.
- internal_note · Bethan Lister 19 May 2026 16:56Query pattern is full table scan across large date range. Index not optimised for this use case. Recommended composite index on client_type and date. Escalated to Samir.
- status_change · 14 Jun 2026 23:59