What happened
What this says
Current to 10 Oct 26Refresh failed to complete by 07:00 on 17 Feb 2026. BB-Demo identified the accounting system API rate-limiting requests and escalated to platform team for tuning.
Problem: The refresh timed out and did not complete by the 07:00 SLA deadline, repeating after Sanne's credential reconfiguration. The accounting system was throttling requests.
Handling: Bethan asked Sanne to restart the connector. The restart was attempted but 07:00 deadline was still missed with a timeout error. Bethan identified rate limiting from the accounting system API and escalated to the platform team.
Watch: Data freshness SLA breach requires platform intervention to handle source API rate limiting.
Details
Updated 9 Oct 26Trail
- created · Sanne Bakker 17 Feb 2026 13:23Accounting system connector sync failed again. Refresh not complete at 07:00 this morning. See previous ticket. This is the second failure after reconfiguring the credential.
- public_reply · Bethan Lister 17 Feb 2026 14:50Can you try restarting the connector from the admin panel? I'll monitor the refresh logs on our side. Let me know once you've done that. Thanks, Bethan
- public_reply · Sanne Bakker 18 Feb 2026 13:38Restarted. Refresh still hasn't completed by 07:00. Last sync shows timeout error. Your accounting system is responding slowly or blocking our requests.
- internal_note · Bethan Lister 18 Feb 2026 16:45Rate limiting issue identified. API enforcing request throttling. Escalate to platform team for ingestion service tuning.
- status_change · 22 Feb 2026 23:59