On March 28, 2024, from 15:57 UTC to 17:50 UTC, some Zendesk customers faced issues updating or publishing new schedules in Tymeshift. This was due to an incorrect application configuration where the service account lacked the necessary…
The March 28, 2024, Zendesk incident was resolved by granting the necessary permissions to the production service account. This action corrected the incorrect application configuration that was preventing schedule updates in Tymeshift. Once the…
The root cause of the Zendesk service incident on March 28, 2024, was an incorrect application configuration. Specifically, the service account did not have the correct permissions to edit or create the schedule service, leading to issues with…
To prevent future incidents similar to the one on March 28, 2024, Zendesk is implementing several remediation items. These include reviewing procedures to incorporate feature flags for future changes, ensuring consistency in application…
For current system status information about Zendesk, you can visit their system status page. This page provides updates on ongoing issues and incidents. Additionally, summaries of post-mortem investigations are usually posted there a few days after…