Thursday August 20, 2020

Incident Summary:

On August 20, 2020 at 9:02 a.m. PDT, some customers began being unexpectedly signed out of Slack on desktop after updating Slack to a newer version. By August 24, 2020 at 4:50 p.m. PDT, reports of this issue subsided without us taking any remediation steps. We are continuing to investigate the root cause of this issue to prevent it from happening in the future.

11:58 AM PST

Thank you for being patient with us. We have resolved the issue where some customers were unexpectedly signed out of Slack on desktop. If you have any further trouble or you need help getting signed back in, please reach out to us at feedback@slack.com. We apologize again for any interruption to your work.

5:52 PM PST

We've received some reports of folks being suddenly signed out of Slack on desktop, and we're investigating this issue further. We apologize for any disruption this may have caused.

10:50 AM PST

Issue summary:
On August 20, 2020 from 8:56 a.m. PDT to 10:04 a.m. PDT, customers may have experienced an “invalid_service” error when attempting to use some slash commands in Slack.

Upon further investigation we found that some slash command requests were timing out due to not receiving a response back from an upstream service provider within the timeframe allotted for these requests. By 10:04 a.m., these requests were no longer timing out and the issue was resolved for all impacted users. This did not require remediation action our end.

12:38 PM PST

We've identified the issue and functionality of slash commands has been restored. Apologies for any trouble this may have caused in the meantime, and if you do run into further trouble let us know at feedback@slack.com

10:09 AM PST

We're currently looking into an issue impacting the use of slash commands. We'll be back with an update once we have more information and we appreciate your patience in the meantime.

9:59 AM PST