What happened
What this says
Current to 10 Oct 26Submission records appeared twice in the brain after the overnight refresh, inflating counts. Bethan Lister found a connector retry loop caused duplicate indexing and deployed a fix.
Problem: The submissions dashboard was showing duplicate records with inflated counts after the refresh, breaking the daily reconciliation with capacity providers. Handling: Bethan found a duplicate index on the submissions connector triggered by a retry loop during the previous night's refresh. She worked with engineering to deploy a fix and rebuild the index overnight. First response took 99 minutes. Watch: Confirm reconciliation counts now match the CRM.
Details
Updated 9 Oct 26Trail
- internal_note · Bethan Lister 2 Oct 2025 12:21Spotted duplicate index on submissions connector during morning monitoring. Refresh log shows a retry loop last night. Escalating to engineering now.
- created · Callum Reid 2 Oct 2025 16:45The underwriting dashboard is showing duplicate records. Submission counts are inflated – records from the latest refresh are appearing twice. This is affecting our daily reconciliation with the capacity providers. Need this sorted by end of day.
- public_reply · Bethan Lister 2 Oct 2025 18:24Hi Callum, I've picked this up and worked with our engineering team on it. We've found the root cause: the submissions connector hit a temporary lock during last night's refresh, which caused the sync to retry and duplicate-index some records. We've deployed a fix to clear the duplicates and rebuild the index. Your dashboard should now show the correct record count. Tonight's nightly refresh will complete the full rebuild. Can you verify that your submission counts are now matching your CRM? Once you confirm it's showing correctly, I'll close this out. Thanks, Bethan
- status_change · 10 Oct 2025 23:59