What happened
What this says
Current to 11 Oct 26Megan reported search slowness across multiple practices as data volumes grew. Bethan explained this was normal data growth and suggested using date filters to speed up queries.
Problem: Searches slowed down as customer indexed more data across multiple practice locations.
Handling: Bethan checked query logs, confirmed searches were running normally for data volume, explained slowdown was natural growth, suggested date filtering. Megan accepted explanation. Ticket solved 2025-09-25.
Watch: Query performance is secondary to freshness, but large result sets can feel like failures. Bethan's explanation turned potential complaint into acceptance.
Details
Updated 9 Oct 26Trail
- created · Megan Statham 8 Sep 2025 11:36Some of our searches are running quite slowly. Especially when we're searching across multiple practices' data at once. Is there anything we can do to improve performance?
- public_reply · Bethan Lister 8 Sep 2025 23:56I've checked your query logs. Your searches are running fine: as you use the system more, data volumes grow naturally and searches take a bit longer. It's nothing to worry about. Filtering by date range can help narrow results if you want faster responses. Thanks, Bethan
- public_reply · Megan Statham 9 Sep 2025 11:05Thanks, that makes sense. We'll try using date filters. That should help us focus on recent issues anyway.
- status_change · 29 Sep 2025 23:59