What happened
What this says
Current to 11 Oct 26Data mismatch between source CRM and brain for shipper city field. Bas Vermeulen raised concern 22 Jun 2026, identified pattern across accounts. Solved 15 Jul 2026. Investigation ongoing.
Problem: Bas Vermeulen reported the city field in the brain showed different values than the source CRM for some shipper accounts. A spot check suggested the pattern applied to multiple accounts and potentially other fields.
Handling: Bethan Lister began investigating connector logs and field mapping on 23 Jun 2026. Bas conducted wider analysis of affected accounts. Progress slowed; the ticket remained open for investigation over two weeks. Solved on 15 Jul 2026 and closed on 19 Jul 2026.
Watch: This is a material data quality issue for a customer heavily dependent on shipper data accuracy. The 23-day resolution time is slow. Evidence shows investigation ongoing after the solved date, suggesting the root cause may not have been fully resolved.
Details
Updated 9 Oct 26Trail
- created · Bas Vermeulen 22 Jun 2026 12:33We've found data mismatches between the source CRM and what's showing in the brain. The city field is incorrect for some shipper accounts. For example, one account shows a different city in the brain than in the CRM source. Has the data validation caught this? Should we be concerned about the accuracy of other fields?
- public_reply · Bethan Lister 23 Jun 2026 03:07Thanks for reporting this. Just so I've got this right: the city field in the brain shows different values than your source CRM for some shipper accounts. Can you give me one specific example of an account where you see the mismatch, which city should it show and which city is it showing?
- public_reply · Bas Vermeulen 23 Jun 2026 09:19One of our key accounts is showing the wrong city in the brain compared to the CRM. I've done a quick spot check on a few others and the pattern seems to be there. Can you trace the field mapping to see where the issue is?
- public_reply · Bethan Lister 25 Jun 2026 16:34I've started checking the connector logs for that field. It could be a mapping issue on our side or something in how the data is being cached during the sync. I'll trace through and get back to you.
- public_reply · Bas Vermeulen 26 Jun 2026 10:04Good, thanks. I'll do a wider spot check in the meantime to see how many accounts are affected and whether other fields have the same problem.
- status_change · 19 Jul 2026 23:59