Zendesk will perform critical maintenance that will impact performance for Chat and Agent Workspace (Support) customers on multiple days in August 2022 during the times listed below:
Date |
Pod |
Start Time |
End Time |
Sun, Aug 14, 2022 UTC |
13, 19 |
07:00 UTC |
08:30 UTC |
(Aug 14, 2022 PDT) |
|
(00:00 PDT) |
(01:30 PDT) |
Sun, Aug 14, 2022 UTC |
23, 27 |
10:00 UTC |
11:30 UTC |
(Aug 14, 2022 PDT) |
(03:00 PDT) |
(04:30 PDT) |
|
Sun, Aug 21, 2022 UTC |
15, 17 |
01:00 UTC |
02:30 UTC |
(Aug 20, 2022 PDT) |
(18:00 PDT) |
(19:30 PDT) |
|
Sun, Aug 21, 2022 UTC |
25, 29 |
04:00 UTC |
05:30 UTC |
(Aug 20, 2022 PDT) |
(21:00 PDT) |
(22:30 PDT) |
Customers Affected: The following customers on the Pods listed above will experience a maximum service disruption of 90 minutes within the maintenance window:
- Zendesk Chat customers
- Agent Workspace customers using Messaging in Support
Please note: Customers who are impacted by the August 14 maintenance will receive a system banner in the Support or Chat interface starting on August 2, 2022 notifying them of this maintenance window, while customers impacted by the August 21 maintenance will receive a system banner in Support or Chat from August 8. Only customers who receive this banner are impacted by this maintenance.
Affected products: Chat, Support (Agent Workspace), Messaging, Web/Mobile Messaging and SunCo SDK
Expected behavior:
During the maintenance window
- Customers using Messaging, Web/Mobile Messaging and SunCo SDK with Agent Workspace will have a degraded experience.
- No new chat sessions can be created. Ongoing chats will be disconnected for both agents and visitors.
- Chat dashboard will be accessible but most of the functionality will be unavailable.
- Agents will not be able to respond to the messaging tickets during the maintenance window.
After the maintenance window
- All Chat, Agent Workspace and Customers using Messaging, Web/Mobile Messaging and SunCo SDK functionality will be restored to normal.
What will happen to our Chat Widget/Mobile SDK/Web SDK during this maintenance?
- If you are currently using the Widget with Messaging enabled, all channels are available for use. However, Agents will only receive messages sent during the maintenance after the window is over. Customers are recommended to redirect customers to contact form, help center, Answer Bot, etc. to ensure end users can expect to reach Agents in a timely manner when they do interact with the Widget.
- If you are currently using the Web Widget (Classic), and other channels outside of Chat are enabled for use (contact form, help center, Answer Bot, etc.), the widget will remain visible on your site through the maintenance window serving those functions besides Chat. Once the maintenance window is over and agents are logged into Zendesk Chat, the Web Widget (Classic) will show the Chat channel as available again.
- If you are using an older version of the legacy Chat Standalone Widget - the widget will not load and be considered offline.
- Chat Mobile SDK and Web SDK will appear offline and will fail to connect.
Why we're doing this:
- The core Chat servers will be restarted after several updates to improve security and reliability of the Chat service and to maintain compliance.
- Increase streaming data store capacity in all pods to accommodate customer traffic growth.
- If any issues are identified while patching the servers, the process will halt and Chat services will be brought back online. We will then work to schedule a new maintenance window to continue as needed.
2 Comments
Following additional testing performed this week, this maintenance will now have up to 90 minutes of downtime (not 60 minutes as originally advertised). This article has been updated to reflect this change. We sincerely apologize for any additional inconvenience this may cause.
We have split the maintenance window into multiple days and adjusted the time to align with the lowest volume period for customers impacted. We have also removed Pod 18 and 28 from this maintenance window. Thanks for your patience while we go through this maintenance work.
Article is closed for comments.