19:21 UTC | 12:21 PT
We’ve been monitoring a fix for the issue impacting Side Conversations for some customers on Pod 17 and are happy to report that the issue is no longer occurring. Please let us know if you have any questions.
12:49 UTC | 05:49 PT
We continue to investigate delivery issues impacting Side Conversations for customers on Pod 17. We will provide further updates as soon as possible.
12:26 UTC | 05:26 PT
We are currently investigating delivery issues impacting Side Conversations for customers on Pod 17. Symptoms include delays and delivery failures for email and Slack side conversations. We will provide an update with more information shortly
From 2020-05-26 06:00 UTC to 2020-05-26 14:25 UTC, customer relying on side conversations experienced a multi-hour delay in delivery and processing for that feature. The incident was caused by Redis workers stopping consuming jobs, leading to our Resque queue filling up our Redis cluster, which prevented workers from restarting. We temporarily raised the Redis memory ceiling for this service, and the queue cleared at a reasonable rate. In order to prevent this from happening again in the future, we are investigating implementing mitigation at the resque-worker level.
FOR MORE INFORMATION
For current system status information about your Zendesk, check out our system status page. During an incident, you can also receive status updates by following @ZendeskOps on Twitter. The summary of our post-mortem investigation is usually posted here a few days after the incident has ended. If you have additional questions about this incident, please log a ticket with us.