Disputed transactions not displaying correctly with large datasets
Ticketclosed
Merriott Lyle Distribution · Disputed transactions not displaying correctly with large datasets
When querying large dispute datasets, transactions were appearing with duplicates and missing sort order. Arjun identified a join logic bug in aggregation that was creating duplicates and losing sort order. The fix was deployed and verified.
What happened
What this says
Current to 13 Oct 26When querying large dispute datasets, transactions were appearing with duplicates and missing sort order. Arjun identified a join logic bug in aggregation that was creating duplicates and losing sort order. The fix was deployed and verified.
Problem: When Merriott Lyle queried large dispute datasets, some transactions appeared twice and sort order was lost. This affected data accuracy during testing with large account datasets.
Handling: Connor reproduced the issue with the large test dataset and looped in Arjun. Arjun quickly identified the root cause: join logic for large datasets was creating duplicates and sort order wasn't being preserved through aggregation. He deployed the fix and Tariq verified it resolved the issue.
Watch: This is a serious data accuracy issue. While resolved, similar bugs may exist in other aggregation queries involving large related record sets. The fact that this affected Merriott Lyle's testing suggests it could impact any customer with large transaction volumes.
Details
Updated 9 Oct 26Trail
created · Tariq Saleem 17 Jul 2025 16:04We're seeing an issue with how the brain displays disputed transactions when there are large numbers of related records. Some disputes aren't showing correctly, and they're not in the right order. It's happening specifically when we test with datasets that have many related items. Can you investigate?- public_reply · Connor Webb 17 Jul 2025 21:03Thanks for reporting this, Tariq. To reproduce it, I need to understand the test scenario better. Can you walk me through the exact steps you're taking when you see this? How many records are you testing with, and what specifically is wrong about the order?
- public_reply · Tariq Saleem 21 Jul 2025 15:07We tested with dozens of disputes linked to each account, with multiple related records per dispute. When we query for disputes, they come back unsorted, and a few appear twice. It's the same test data we used with the performance issue you addressed before.
- public_reply · Connor Webb 22 Jul 2025 13:21I can reproduce it with the large dataset. I'm seeing duplicates and missing sort order in the output. Let me loop in Arjun to look at the query logic.
- internal_note · Connor Webb 24 Jul 2025 10:45Arjun found it. The join logic for large datasets is creating duplicates, and sort order isn't preserved through aggregation. Fix deployed.
- public_reply · Tariq Saleem 24 Jul 2025 15:18Just tested with the new version and it's working now, disputes are displaying in the right order with no duplicates. Great turnaround, thanks.
- status_change · 8 Aug 2025 23:59