What happened
What this says
As at Fri 9 Oct 2026Nikhil reports Calls connector timeout before 07:00 completion, blocking key-account team from latest call recordings. Root cause: concurrent warehouse load on customer's Snowflake instance. Olivia restarts refresh (expected within 30 minutes). Recommends warehouse scaling review.
Data freshness and support SLA issue. Enterprise SLA requires nightly completion by 07:00; timeout prevents that. First response 123 minutes misses Enterprise P1 target of 30 minutes.
Problem: Timeout is partially customer-owned (warehouse scaling) but BG-Demo still missed first response SLA. Root cause correctly identified by Olivia.
Watch: Enterprise SLA credit likely owed for both first response miss and data freshness breach. Customer needs to optimise Snowflake warehouse scaling.
Details
Updated 9 Oct 26Trail
- Internal note · Olivia Grant 13 Jun 2025 12:18Refresh timeout alert just triggered for Calls connector at 06:59. Checking load metrics. Nikhil likely to report.
- created · Nikhil Rao 13 Jun 2025 12:27The Calls connector refresh timed out this morning before 07:00 local completion time. Load started at 06:55 but didn't finish. This is blocking our key-account team from seeing latest call recordings and is a priority. Connector worked fine yesterday. Can you investigate and restart the load? Nikhil
- Public reply · Olivia Grant 13 Jun 2025 14:30Hi Nikhil, I've picked this up. The timeout was caused by concurrent query load on your Snowflake warehouse during the sync window. I've restarted the refresh and it's running now, should finish within half an hour. I'd recommend reviewing your warehouse scaling settings with your DBA to handle concurrent queries during the nightly window. I'll confirm once it's done. Olivia
- Status change · 23 Jun 2025 23:59