Bethan Lister

Refresh not complete at 07:00 Amsterdam

Ticketclosed

Veldmaat Payments: documents logo Veldmaat Payments: documents · Refresh not complete at 07:00 Amsterdam

Refresh not completing by 07:00 Amsterdam time (three delays of 7–18 minutes over three days); Exact Online API pagination is bottleneck; customer indexing tens of thousands of records per run.

Priority high

What happened

What this says

Current to 10 Oct 26

Refresh not completing by 07:00 Amsterdam time (three delays of 7–18 minutes over three days); Exact Online API pagination is bottleneck; customer indexing tens of thousands of records per run.

Problem: Sanne reported refresh delays of 7–18 minutes past the 07:00 target on three consecutive days. Handling: Bethan requested refresh logs and record counts. Sanne provided logs on 6 May 2026 showing Exact Online connector as the bottleneck; tens of thousands of records indexed per run. Internal analysis identified Exact Online API pagination as the cause, not BB-Demo infrastructure.

Watch: Pattern of delays suggests higher-than-baseline load or API response issues on vendor side. No escalation to platform team shown in resolved ticket.

AI · claude-haiku-4-5-20251001 · 10 Oct 2026

Details

Updated 9 Oct 26
Priorityhigh
Statusclosed
Categorydata_freshness
Channelemail
First response (min)143
CSAT5
Helpdeskmade from

Trail

  1. Sanne Bakker
    created · Sanne Bakker 1 May 2026 17:41
    Refresh not complete at 07:00 Amsterdam. Last three days: 07:12, 07:18, 07:14. Pattern of delays. Checking on your side? Sanne
  2. Bethan Lister
    public_reply · Bethan Lister 1 May 2026 20:04
    Thanks for those timestamps, Sanne. Can you share one of the refresh logs from the past couple of days? That'll let me see where the bottleneck is. Also, how many records are we indexing on each run? Thanks, Bethan
  3. Sanne Bakker
    public_reply · Sanne Bakker 6 May 2026 13:53
    Logs attached. Ingestion is taking longer than expected. Exact Online connector is the slowest. We're indexing tens of thousands of records per run. Sanne
  4. Bethan Lister
    internal_note · Bethan Lister 6 May 2026 14:13
    Logs show Exact Online API responding slowly. Pagination is the bottleneck. Customer's volume is high but manageable. Need Ewan to review connector polling rate.
  5. Bethan Lister
    status_change · Bethan Lister 11 May 2026 14:24
  6. status_change · 15 May 2026 23:59
Helpdeskmade from

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
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

Ask B

Ask B

B-Brain · read-only