Zendesk Service Incident March 28, 2024 Explained
What happened during the Zendesk service incident on March 28, 2024?
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 permissions. The issue was resolved by granting the required permissions to the service account. For more details, you can check theoriginal link.
More related questions
How was the March 28, 2024, Zendesk incident resolved?
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…
What caused the Zendesk service incident on March 28, 2024?
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…
What steps are being taken to prevent future Zendesk incidents like the one on March 28, 2024?
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…
Where can I find more information about Zendesk system status and incidents?
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…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
