What happened
What this says
As at Fri 9 Oct 2026Bas Vermeulen reported account status fields showing different values in brain versus CRM after customer's data cleanup. Bethan Lister identified missing modified timestamp update in CRM records.
Problem: Account fields out of sync after customer's CRM cleanup, causing report discrepancies. Root cause was CRM's modified timestamp not updating during cleanup, so the brain did not detect changes. Handling: BG-Demo traced sync logs and directed customer to re-save records with fresh timestamp. First response was slow (874 minutes).
Details
Updated 9 Oct 26Prioritylow
Statusclosed
Categorydata_quality
Channelemail
First response (min)874
Helpdeskmade from
Trail
- created · Bas Vermeulen 22 Jun 2026 12:33We're noticing that some shipper account fields show different values in the brain compared to our CRM. For example, account status shows differently in both systems. This is causing discrepancies in our reports.
- Public reply · Bethan Lister 23 Jun 2026 03:07Thanks for reporting this, Bas. I can help investigate. Which specific fields are showing mismatches, and do you know if the CRM data was recently updated?
- Public reply · Bas Vermeulen 23 Jun 2026 09:19It's mainly the status field. Some accounts show as active in the CRM but appear inactive in the brain. We ran a data cleanup in the CRM a few days ago.
- Public reply · Bethan Lister 25 Jun 2026 16:34Thanks for that. I've checked the sync logs and the update did come through, but I think the issue might be that the CRM record's modified timestamp didn't update. Can you check the record modified dates in your CRM? If they're old, we might not have picked up the change.
- Public reply · Bas Vermeulen 26 Jun 2026 10:04Ah, I see. The modified date didn't update during the cleanup. I've re-saved the records with a fresh timestamp now. Should it pick up on the next refresh?
- Status change · 19 Jul 2026 23:59
Helpdeskmade from