What happened
What this says
Current to 11 Oct 26Salesforce connector was running a day behind because an internal password reset was not reflected in Kingdon's connector configuration. Ryan identified and fixed the credential issue on his side.
Problem: Salesforce data in the brain was one day behind current, even though the nightly refresh had completed successfully and other connectors were working normally.
Handling: Olivia asked diagnostic questions about credentials and permissions. Ryan checked and discovered that a colleague had reset the Salesforce sync user's password internally but had not updated it in their connector configuration. After Ryan updated the credentials, the connector caught up.
Watch: Silent sync failures may occur after system changes the customer makes without notifying BB-Demo.
Details
Updated 9 Oct 26Trail
- created · Ryan Heslop 13 Apr 2026 08:48Hi, I've noticed that our Salesforce data in the brain is showing records from yesterday, not today. The nightly refresh ran successfully according to our logs, but it doesn't look like new records from Salesforce have come through. The other connectors are working normally. Is this something you've come across? Cheers, Ryan.
- public_reply · Olivia Grant 13 Apr 2026 15:40Thanks for the detail, Ryan. A few quick checks: can you confirm that the connection credentials in your Salesforce integration haven't changed recently? It's possible something like a password reset or permission change could stop the sync silently. Let me know what you find. Olivia.
- public_reply · Ryan Heslop 15 Apr 2026 15:07Found it! A colleague had reset the Salesforce sync user's password last week but didn't update it in our end. We've fixed that now and the connector is catching up with today's records. Thanks for pointing us in the right direction. Cheers, Ryan.
- status_change · 21 Apr 2026 23:59