What happened
What this says
As at Fri 9 Oct 2026Ryan Heslop reported nightly refresh incomplete mid-morning on 18 Jun 2026; missing reporting-turnaround tickets blocked SLA tracking. Olivia found reporting-turnaround connector hit temporary sync error; reset and full refresh completed 22 Jun 2026.
Problem: Ryan Heslop reported refresh not complete by mid-morning on 18 Jun 2026, blocking daily standup and SLA tracking across trusts. Missing reporting-turnaround tickets from that day.
Handling: Olivia Grant investigated refresh logs and found the reporting-turnaround connector hit a temporary sync error. She reset the connector; full refresh completed 22 Jun 2026. Internal investigation revealed API rate limit hit on the ticket source.
Watch: Rate limit hit on high-volume connector indicates potential recurrence risk. Platform team noted need to review batch sizing for high-volume accounts. Confirm fix prevents API limit issues on future refreshes.
Details
Updated 9 Oct 26Trail
- created · Ryan Heslop 18 Jun 2026 09:10The refresh hasn't completed yet and it's now mid-morning. We're missing today's reporting-turnaround tickets and it's affecting our ability to track SLAs across the trusts. This is a blocker for our daily standup.
- Public reply · Olivia Grant 18 Jun 2026 11:31I'm on it. Checking the refresh logs now and will update you in the next half hour.
- Public reply · Olivia Grant 22 Jun 2026 16:04It was the reporting-turnaround connector, looks like one of your ticket sources hit a temporary sync error. We've reset it and it's pulling again. Full refresh completed this morning.
- Internal note · Olivia Grant 23 Jun 2026 10:44API rate limit hit on ticket source. Platform team to review batch sizing for high-volume accounts.
- Public reply · Ryan Heslop 23 Jun 2026 13:09Understood. Is this likely to happen again, or have you fixed it permanently?
- Status change · 29 Jun 2026 23:59