Zendesk resolved the Chat trigger issue by rolling back a recent deployment that was causing the triggers to fire incorrectly. This rollback was completed across all pods, and the situation was monitored until full resolution was confirmed.
The root cause was a new mechanism for evaluating Chat trigger conditions that skipped certain scenarios. To fix this, a new software version was deployed to address the evaluation gap. Additional measures, such as anomaly detection and more comprehensive testing, are scheduled to prevent future occurrences.
On August 15, 2024, Zendesk experienced a service incident where Chat triggers were firing unexpectedly. This issue affected chat tagging, routing, and the sending of automated messages, leading to unexpected Chat behavior for customers. The…
The root cause of the Zendesk Chat trigger incident was a new mechanism for evaluating Chat trigger conditions. This mechanism skipped certain scenarios, which resulted in the default action of firing off trigger actions unexpectedly. To address…
To prevent future Chat trigger issues, Zendesk is implementing several remediation items. These include adding anomaly detection for unusual volumes of trigger actions and implementing additional tests to cover more complex condition scenarios….
The Zendesk Chat trigger incident on August 15, 2024, lasted from 09:45 UTC to 13:19 UTC. During this time, customers experienced unexpected Chat behavior due to triggers firing incorrectly. The issue was resolved by rolling back a recent…