What happened
What this says
As at Fri 9 Oct 2026Veldmaat Payments' nightly data refresh finished at 07:20 instead of 07:00 on 1 Jun 2026. Bethan Lister identified the Exact Online connector's API responding slowly as the cause, a third-party issue not attributable to BG-Demo.
Problem: Sanne Bakker reported that the nightly refresh did not complete by the 07:00 deadline on 1 Jun 2026, finishing at 07:20. The ticket was marked high priority. Handling: Bethan Lister responded in just over two hours and investigated the refresh logs. She found that the Exact Online connector's API was responding slowly, which slowed the overall job. No errors occurred in BG-Demo's systems and no changes had been made to the customer's data or connectors. Watch: The issue was external to BG-Demo and resolved naturally. Monitor whether the Exact Online connector continues to experience API slowness in future refresh cycles, as a recurring pattern could indicate a deeper issue.
Details
Updated 9 Oct 26Trail
- created · Sanne Bakker 1 Jun 2026 08:55Refresh not complete at 07:00 again. Started late again, finished 07:20 this morning. Sanne
- Public reply · Bethan Lister 1 Jun 2026 10:53Hi Sanne, I'm seeing the refresh logs. Looks like it kicked off around 22:55 last night but took longer than usual to process the data. Can you confirm if anything changed on your side – added connectors, increased data volume, or any system changes in the past week? Thanks, Bethan
- Internal note · Bethan Lister 1 Jun 2026 12:17Spoke to Sanne. No changes on their side. Refresh job running slower than baseline. Exact Online connector is the bottleneck – their API responding slowly. No errors in ingestion logs. Issue on the API side, not ours.
- Status change · 7 Jun 2026 23:59