What was said
What this says
Current to 11 Oct 26Holly Tranter confirmed the sync failures came from credentials the customer withdrew on the CTO's instruction while systems move to an in-house warehouse. They will not be reissued, so the connectors are retired.
Ask: Holly Tranter told Dominic Hale the sync failures were not a BB-Demo fault and asked what was needed to close the tickets. Anjali Desai was copied as the access decision sits with information security, and does not reply in the thread.
Customer view: on 23 Mar 2026 Holly confirmed the withdrawal was deliberate and that the connectors should be treated as retired. She warned that this changes how much the brain is used.
Next: Dominic marked the connectors retired and closed the sync tickets on 24 Mar 2026. Daniel Okafor picks up the wider conversation with Saskia Mendes.
The thread
Updated 9 Oct 26Messages
- Holly Tranter 17 Mar 2026 13:46Hi Dominic, A heads-up before your team spends any more time on this. You will have seen a run of sync failures from our side over the last few days. That is because the credentials the brain was using for some of our systems have been withdrawn here. It was not a fault on your end. I have copied Anjali, as the access decision sits with information security rather than with me. Could you let me know what you need from us to close the open tickets cleanly, and whether anything else will break when the connections drop? Thanks, Holly Holly Tranter Business Systems Analyst, Delancey Haig
- Dominic Hale 19 Mar 2026 11:43Hi Holly, hi Anjali, Thanks for the note. I've taken ownership of this and I have copied Daniel, who looks after the account. Here's what we know. The four tickets raised this month are all connector sync failures, and they line up with the credentials being rejected from the source systems. Nothing on the BB-Demo side has changed, and the brain itself is available. Here's what we do not know: whether the withdrawal is meant to be temporary, and whether you want the connections reissued. Could one of you confirm two things? - Was the withdrawal deliberate? - If so, should we expect new credentials, or should we stop retrying and mark those connectors as retired? Until I hear from you I will leave the connectors paused so they stop generating failures. Next update by 16:00 on Monday. Thanks, Dominic
- Holly Tranter 23 Mar 2026 16:21Dominic, Sorry for the delay, I wanted to get a proper answer rather than guess. Anjali and I have both checked. Yes, it was deliberate. The credentials were withdrawn on the CTO's instruction while those systems move across to our in-house warehouse. They will not be reissued. Please treat those connectors as retired rather than broken. Anjali, please add anything I have missed on the security side. I am conscious this changes how much we use the brain, and I would rather you heard it from us now than found it in the usage numbers. Saskia knows the direction of travel and I expect she will be in touch with Daniel. Holly
- Dominic Hale 24 Mar 2026 14:40Hi Holly, hi Anjali, Thank you, that is clear and I appreciate the straight answer. Here's what I am doing on our side: - The affected connectors are marked as retired, not faulty, so they will no longer retry or raise alerts. - I am closing the open sync tickets with a note that the withdrawal was intentional and that no credentials will be reissued. - I have written up the timeline so nobody has to chase the history later. If you change your mind about any of the systems, tell Daniel and we will set the connection up again with fresh credentials from you. Otherwise there is nothing further needed from your team on support. Daniel will pick up the wider conversation with Saskia. Next update from me only if something changes. Thanks, Dominic