On January 26, 2022 at 4:30 p.m. PST to January 28, 2022 at 1:59 p.m. PST, a subset of users received banner notifications for thread replies even though they had the “Notify me about replies to threads I’m following” preference turned off.
This was caused by a code change which unintentionally turned that setting on for the affected users.
A fix was deployed and no further users will be impacted going forward.
4:38 PM PST
We have resolved the underlying issue for this incident and no further users will be impacted going forward.
Users previously impacted by this issue may still find the "Notify me about replies to threads I'm following" preference changed from what was previously selected. To remedy this, please go to Preferences > Notifications and update this preference if needed.
2:43 PM PST
Some users have been unexpectedly receiving banner notifications for replies in threads they're following when the preference to receive them was not previously enabled. We've released a change, and believe that no additional users will be impacted by this issue. However, we are continuing to monitor the situation and will report back once we have another update.
Please be aware that users previously impacted by this issue may find their "Notify me about replies to threads I'm following" preference changed from what was selected previously. We recommend heading to Preferences > Notifications and toggling this preference if needed.
4:31 PM PST
As we continue to investigate this issue we wanted to quickly note that toggling the "Notify me about replies to threads I'm following" in your "Notifications" settings should help as a workaround. Thank you for your patience as we work through this one!
11:45 AM PST
Some users are unexpectedly receiving banner notifications for replies in threads they're following when the preference to receive them was not previously enabled. We're investigating and will let you know as soon as we know more.
10:19 AM PST
On January 27, 2022 at 3:44 p.m. PST to January 28, 2022 at 10:45 a.m. PST, users were unable to use the “Jump to…” date button.
This was caused by a code change which led to the button being unresponsive to click action.
A fix was deployed and the "Jump to..." date button is functioning as intended. If you are still experiencing this issue, please reload your client by using "Command + Shift + R" on Mac, or "Control + Shift + R" on Windows/Linux.
1:10 PM PST
This has now been resolved. Please reload Slack using Cmd/Ctrl + Shift + R in order for the fix to be reflected on your end. Thank you for your patience.
10:54 AM PST
We've identified the cause of the issue and will be releasing a fix shortly. Apologies for the trouble in the meantime.
9:42 AM PST
Some users are unable to use the "Jump to date" button in channels. We’re investigating and will let you know as soon as we know more.
9:31 PM PST
On January 27, 2022 from 5:30 a.m. to 1:06 p.m. PST, some users may not have received 2FA SMS messages for signing in to Slack.
This was traced back to an upstream provider that was experiencing issues with a hardware configuration. The upstream provider resolved the problem, and affected users began receiving 2FA SMS messages once again.
7:57 PM PST
The issue for users not receiving their 2FA SMS codes has now been resolved. If you continue to experience any trouble, please reach out to us at firstname.lastname@example.org.
3:00 PM PST
Some customers are unable to receive 2FA (two-factor authentication) SMS messages. This is due to an issue experienced by one of our upstream partners. We are investigating further and will share back when we have more updates.
7:13 AM PST