A configuration error on Salesforce's side invalidated OAuth tokens across Zendesk's Salesforce integration, rendering the Ticket Viewer inaccessible and disrupting data synchronisation between the two platforms from 29 May through 8 June 2026. The incident affected customers across all pods, with initial troubleshooting steps proving ineffective because the root cause lay outside Zendesk's control. Zendesk's response timeline reveals a critical vulnerability in cross-platform integrations: the company spent nearly three days investigating and deploying workarounds before identifying that Salesforce's security settings were the culprit. This raises an important question for teams managing mission-critical integrations—how visible is your vendor's incident response when the problem originates with a third party, and what contingency protocols exist when your primary platform cannot immediately resolve the issue?
The incident's resolution required customers to perform a manual disconnect-reconnect cycle to refresh invalidated tokens, a remediation step that placed operational burden on support teams already managing the fallout. Zendesk's post-incident analysis identified gaps in alert sensitivity, documentation accuracy, and monitoring coverage for partner integrations, suggesting that the company had insufficient observability into Salesforce-side configuration changes that could cascade into production incidents. For CX leaders operating in hybrid Salesforce-Zendesk environments, this incident underscores a structural risk: integration health depends on both vendors' operational discipline, yet visibility and control remain asymmetrical. Teams relying on Salesforce Ticket Viewer for omnichannel workflows experienced genuine service degradation without the ability to self-remediate until Zendesk deployed a workaround, then required manual intervention once the permanent fix was deployed.
The remediation roadmap—enhanced monitoring, improved documentation, clearer escalation procedures, and closer partner coordination—addresses the symptoms rather than the systemic fragility of tightly coupled integrations. For organisations considering deeper Salesforce-Zendesk integration or those already dependent on Ticket Viewer functionality, this incident demonstrates that integration robustness cannot be assumed even between mature, enterprise-grade platforms. The question becomes whether your team's incident response protocols account for scenarios where your primary vendor is reactive rather than proactive, and whether your architecture includes fallback pathways when cross-platform features fail.
SummaryBetween May 29, 2026, 07:41 UTC and June 1, 2026, 01:54 UTC, customers using Salesforce Zendesk Ticket Viewer and Canvas app across multiple pods experienced blank pages and access errors that prevented viewing Zendesk tickets. Additionally, some customers faced disruptions in synchronizing d