Thursday April 4, 2024

Incident
Some users aren't receiving 2-FA codes

Issue summary: From March 15, 2024, at around 3:50 PM PDT until April 4, 2024 at 2:49 PM PDT some users were not able to receive a two-factor authentication (2FA) code. This was traced to a routine change to a backend service responsible for requesting the authentication codes to be sent. This backend service had stale data and as a result, errors occurred when authentication codes were attempting to generate. We updated the backend service to receive the correct data, resolving the issue for all users.
3:29 PM PST
The issue with receiving two-factor authentication (2FA) codes has been resolved, users should no longer encounter trouble. We apologize for any interruptions to your day and appreciate your patience as we worked to sort this out.
2:51 PM PST
We're investigating an issue where some users aren't receiving two-factor authentication (2FA) codes to log into GovSlack. We'll be back with another update once we have news to share.
1:37 PM PST
Features affected
Login/SSO
Status
Incident

Incident
Users receive an error message when attempting to rename a channel.

Issue Summary: From April 4, 2024 at 12:30 PM PDT to April 4, 2024 at 10:20 PM PDT, some customers were receiving this error message when trying to rename a channel: “Oops/Whoops, something went wrong with renaming the channel. Please try again.” We identified a code change which inadvertently altered the permission to edit channel. This resulted in this error being shown. We rolled back this change, correcting the issue. Impacted customers should no longer experience any further trouble after reloading their Slack. To reload Slack use Command + Shift + R on Mac and Ctrl + Shift + R on Windows/Linux.
1:22 AM PST
We've released a fix and channel renaming should be back to normal now. We apologize for the disruption to your work.
10:28 PM PST
Multiple users are reaching out reporting that they receive an error message when trying to rename a channel: “Oops/Whoops, something went wrong with renaming the channel. Please try again.” We're investigating the issue and will report back here with more information and workarounds to share.
8:34 PM PST
Features affected
Workspace/Org Administration
Status
Incident