What happened
What this says
Current to 12 Oct 26Zendesk connector stopped loading excursion tickets. Callie and Rory traced the issue to a custom field added in Zendesk that broke the field mapping, fixed it within hours, and the customer confirmed data was restored.
Problem: high-priority data availability issue; Zendesk connector stalled after a custom field was added to the source system, stopping new ticket ingestion.
Handling: support team diagnosed stalled sync, identified the root cause (custom field breaking the mapping), and engineering patched the connector quickly. Customer confirmed visibility restored and praised the fast resolution.
Watch: customer has client-facing dependency on data freshness; connector failures have immediate business impact.
Details
Updated 9 Oct 26Trail
- created · Kerensa Trelease 8 Feb 2024 16:56The Zendesk connector stopped loading excursion tickets. We've had several new tickets since this morning but nothing's coming through to the brain. This is urgent. The clients need to see their data.
- public_reply · Callie Brennan 8 Feb 2024 19:48Hi Kerensa, I can see the sync has stalled. First thing: can you check that the API token in Zendesk is still valid? If that's fine, tell me when the last ticket came through and I'll check our logs.
- public_reply · Kerensa Trelease 12 Feb 2024 09:23Token's fine. Last update was Tuesday at 06:30. Three new excursions since then and none in the brain. Not good.
- internal_note · Callie Brennan 13 Feb 2024 11:00Zendesk added a custom field yesterday and it's broken the field mapping. Rory's patching now. Should be live within the hour.
- public_reply · Callie Brennan 13 Feb 2024 11:43Found it: custom field added yesterday broke the mapping. Rory's patching now and we should have the load working within an hour. I'll update you once it's live.
- public_reply · Kerensa Trelease 13 Feb 2024 16:35Data's back. Clients can see their tickets now. Well done on the quick fix. Cheers, Kerensa
- status_change · 17 Feb 2024 23:59