What happened
What this says
Current to 10 Oct 26Refresh 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.
Details
Updated 9 Oct 26Trail
- created · Sanne Bakker 1 May 2026 17:41Refresh not complete at 07:00 Amsterdam. Last three days: 07:12, 07:18, 07:14. Pattern of delays. Checking on your side? Sanne
- public_reply · Bethan Lister 1 May 2026 20:04Thanks 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
- public_reply · Sanne Bakker 6 May 2026 13:53Logs attached. Ingestion is taking longer than expected. Exact Online connector is the slowest. We're indexing tens of thousands of records per run. Sanne
- internal_note · Bethan Lister 6 May 2026 14:13Logs show Exact Online API responding slowly. Pagination is the bottleneck. Customer's volume is high but manageable. Need Ewan to review connector polling rate.
- status_change · 15 May 2026 23:59