What happened
What this says
As at Fri 9 Oct 2026Abbie reported that the calls connector had not synced new data for over 24 hours. Olivia and Samir identified a timeout in the call recorder API and retried the job.
Problem: Abbie Gaskarth reported that the calls connector was frozen and had not synced new data since yesterday morning, despite her call recorder integration working normally.
Handling: Olivia investigated the sync logs and identified an API timeout. Samir Haddad confirmed the root cause was the API returning a slowdown on one request. The job was retried.
Watch: Data freshness risk; the connector stalled for at least 24 hours. An internal note flagged a need for more graceful retry logic in future API timeouts. Monitor for recurrence.
Details
Updated 9 Oct 26Trail
- created · Abbie Gaskarth 27 Mar 2026 17:13Hi, I've noticed the calls connector hasn't synced any new data since yesterday morning. The records seem frozen. I checked our call recorder integration and it looks fine on that end. Any ideas what might be blocking it? Cheers, Abbie
- Public reply · Olivia Grant 28 Mar 2026 00:01Hi Abbie, Thanks for reporting. I'm looking into the sync logs now. Let me investigate further and I'll update you as soon as I have more information. Olivia
- Internal note · Olivia Grant 28 Mar 2026 11:11Found the issue: timeout in the call recorder API. Root cause is the API returned a slowdown on one request. Retried the job; should sync now. On us to retry more gracefully.
- Status change · 5 Apr 2026 23:59