Ask
Delancey Haig: documents logo

Connector credentials withdrawn on our side

Email thread

Delancey Haig: documents logo Delancey Haig: documents · support

Holly 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.

What was said

What this says

Current to 11 Oct 26

Holly 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.

AI · claude-sonnet-5-5 · 11 Oct 2026

The thread

Updated 9 Oct 26
Typesupport
Messages4
First message2026-03-17
Last message2026-03-24

Messages

  1. Holly Tranter
    Holly Tranter 17 Mar 2026 13:46
    to Dominic Hale
    Hi 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
  2. Dominic Hale
    Dominic Hale 19 Mar 2026 11:43
    to Holly Tranter, Anjali Desai
    Hi 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
  3. Holly Tranter
    Holly Tranter 23 Mar 2026 16:21
    to Dominic Hale
    Dominic, 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
  4. Dominic Hale
    Dominic Hale 24 Mar 2026 14:40
    to Holly Tranter, Anjali Desai
    Hi 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

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only