What happened
What this says
Current to 14 Oct 26Multi-dataset queries timing out after one minute on orders and returns data. Kate identified indexing backlog on returns connector and cleared it. Performance restored.
Problem: Search queries across orders and returns datasets were timing out after approximately one minute, blocking real-time answers during client calls.
Handling: Kate isolated the issue to an indexing backlog on the returns connector and resolved it, eliminating the performance bottleneck.
Watch: Indexing backlogs indicate data freshness risk. Monitor returns connector loads regularly to prevent recurrence, particularly during high-usage periods.
Details
Updated 9 Oct 26Trail
- created · Josh Pearce 30 Mar 2026 14:54The brain is taking a long time to return results on some of our queries. Search results are particularly delayed when querying across multiple datasets. This is affecting our ability to get quick answers during client calls.
- public_reply · Kate Ormerod 30 Mar 2026 16:47Thanks for reporting this, Josh. Just so I've got this right: you're seeing slowness on search queries across multiple datasets. Which datasets are you experiencing the delay with, and roughly how long is it taking to get results back?
- public_reply · Josh Pearce 31 Mar 2026 09:32It's mainly orders and returns data. The queries are timing out after about a minute. This started yesterday afternoon without any changes on our side.
- public_reply · Kate Ormerod 2 Apr 2026 14:03Thanks for the detail. I've identified an indexing backlog on the returns connector. I've cleared it now and results should be back to normal speed. Can you run one of those queries again and let me know if it's faster?
- status_change · 19 Apr 2026 23:59