What happened
What this says
Current to 10 Oct 26Craig Paterson reported the connector timing out during refresh on 4 Jul 2025. After investigation, the root cause was identified as an API endpoint redeploy on the source system with new rate limits. The customer's IT team added BB-Demo to the allowlist to resolve it.
Problem: The connector hung during refresh after timing out on payload retrieval, suggesting a source system change.
Handling: Bethan asked about recent deployments. Craig identified an API endpoint redeploy with rate limit changes and coordinated with his IT team to add BB-Demo to the allowlist.
Watch: Resolved. The root cause was external (customer's source system), not a BB-Demo bug. The ticket shows good customer-side troubleshooting and coordination.
Details
Updated 9 Oct 26Trail
- created · Craig Paterson 4 Jul 2025 10:02Just to flag - that's the connector timing out again. The refresh started at 23:30 yesterday but it's still hanging. The last payload was at 01:47 this morning, nothing since. I'll keep an eye on it. Regards, Craig
- public_reply · Bethan Lister 4 Jul 2025 22:31Hi Craig, thanks for the information. Can you check whether anything changed with the source system in the last week - any deployments? Thanks, Bethan
- public_reply · Craig Paterson 7 Jul 2025 13:03There was a deployment last Tuesday but nothing that would affect the API. I'll check with the team. Regards, Craig
- public_reply · Craig Paterson 9 Jul 2025 10:23Found it - they redeployed the API endpoint and changed rate limits last Tuesday. They're adding us to the allowlist now. Regards, Craig
- internal_note · Bethan Lister 9 Jul 2025 11:18Root cause: API endpoint redeploy. Endpoint team adding customer to allowlist.
- status_change · 1 Aug 2025 23:59