Friday April 29, 2022

Incident

Some users are being signed out, and unable to sign back in

Issue summary:
From 10:30PM on April 29, 2022 until 4:21PM PDT on April 30, 2022, some users were being signed out of their workspace with a Server Error “Sorry, something went wrong” and were unable to log back in.

We traced the cause of the issue back to a change made earlier in the day that resulted in some server disk space running low. We subsequently cleared space on the affected database, resulting in immediate recovery. With this, we’ve resolved the issue, and all impacted customers should now be able to access Slack.

7:47 PM PST

We've resolved the issue, and all impacted customers should now be able to access Slack. You may need to reload Slack (Cmd/Ctrl + Shift + R) to see the fix on your end. Thanks for bearing with us and we apologize for keeping you away from your work.

8:38 AM PST

We’re starting to see some steady improvements, but we still have some work to do. We'll share another update when things are working as they should.

Thank you again for your patience while we investigate this further.

1:52 AM PST

We've identified the root cause of this issue, and we're actively investigating remediation for affected customers.

Thank you for your patience while we look into this. We'll share another update in 60 minutes.

12:42 AM PST

Some users are being signed out of their workspace sessions, and seeing a server error when attempting to sign back in.

We're currently investigating the source of this issue, and we will have another update as soon as there is further information to share. We apologise for the disruption in the meantime.

11:43 PM PST

Services affected

Login/SSO

Connections

Status

Incident

Incident

Error with using threads

Issue summary:

On April 27, 2022 at 11:00 AM PDT until 5:18 PM PDT, some customers may have seen errors when trying to use threads. From our investigation, we identified the problem to be caused by a recent code update that caused an issue with how messages in threads were rendered. Reverting that update fixed the issue for all affected customers.

3:15 PM PST

Services affected

Messaging

Status

Incident

Incident

Issues loading threads or mentions & reactions

Issue Summary:

Between 8:18 AM to 8:32 AM PT some users received a "Something's fishy" error while loading their threads or mentions & reactions from the sidebar.

We closely monitored incoming reports and internal metrics and are confident the issue is now resolved. For those affected, please use Cmd/Ctrl + Shift + R to do a hard reload. We're continuing to investigate the cause of the issue to prevent future occurrences.

11:06 AM PST

Services affected

Messaging

Status

Incident