What happened
What this says
As at Fri 9 Oct 2026Nikhil Rao reported queries running slower after adding a new CRM source with large volume. Bethan Lister identified the issue as missing indexes for the new data and escalated to engineering for optimization.
Problem: Query response times increased noticeably after a new CRM connector brought in many records. Full table scans were most affected. Handling: First response came after 262 minutes on 2 Sep 2025. Bethan confirmed the issue and identified that indexes were not optimized for the new data volume, then escalated to engineering. Watch: Heavy user with configuration changes; confirm performance recovery.
Details
Updated 9 Oct 26Trail
- created · Nikhil Rao 1 Sep 2025 15:36Queries are running much slower than normal over the last couple of days. I ran the refresh job yesterday and it completed normally, but something has changed since then. Users are reporting slow response times when running searches and accessing records. Can you investigate what might have changed?
- Public reply · Bethan Lister 1 Sep 2025 19:58Thanks for reporting. I've picked this up. Can you describe what you mean by slower? Are queries that normally complete quickly now taking much longer, or are they hanging? Has anything changed on your side: new connectors added, more data sources, any configuration changes? Thanks, Bethan
- Public reply · Nikhil Rao 2 Sep 2025 09:25Query response times have increased noticeably over the last day. I checked the load history and the refresh completed normally. The only change is we added a new CRM source which brought in a large volume of records. That's the only variable. Queries running full table scans are most affected. Nikhil
- Internal note · Bethan Lister 2 Sep 2025 09:47New CRM source with large record volume added. Full table scans degraded. Check whether indexes are optimized for new data volume. Escalate to Ewan for query optimization and schema review.
- Status change · 13 Sep 2025 23:59