Monday May 5, 2025

On May 2, 2025 from 4:34 PM PDT to May 5th, 2025 at 12:24 PM PDT, users may have had trouble switching to the Archived or the Completed views of the Later tab, as well as problems marking their items as archived or completed.

We made a code change that inadvertently prevented state changes for Later items. We rolled back this change, restoring full functionality to this feature.

5:01 PM PST

The issue with the Later tab on the desktop app and browser has been resolved. We appreciate your patience as we sorted this out and apologies for any disruption to your workday.

1:12 PM PST

We’ve identified the cause of the issue with the Later tab and we’re working on getting a fix out as soon as possible. 

We’ll be back once we have another update to share.

10:48 AM PST

We’re looking into an issue impacting the Later tab on the desktop app and browser. 

Users may be having trouble switching from the `In Progress` tab to the `Archived` or `Completed` tab. Items may also be missing from the `Archived` or `Completed` tabs. 

We’re investigating and will let you know as soon as we know more. We appreciate your patience in the meantime.

10:02 AM PST

On May 5, 2025 from 2:41 PM PDT until 10:31 PM PDT, users experienced issues affecting message sending and Threads functionality. The issues stemmed from a code change that incorrectly routed database queries to primary servers instead of replicas, causing instability in our database infrastructure.

The incident was automatically detected when our database management system encountered issues with its operations. Our engineering teams identified the root cause and implemented a fix by reverting the problematic code change. Service was fully restored after the code reversion.

We apologise for any disruption this may have caused.

2:35 AM PST

This is now resolved for all affected users and Slack should be running as normal once more.

Thank you for your patience and understanding as we worked to fix this. 

11:19 PM PST

We have deployed the fix and are monitoring the situation to be sure that this will fully resolve this problem for all impacted users. We'll provide an update as soon we're able to confirm that everything is back to normal. 

11:09 PM PST

We're still working to get the fix out to everyone. We'll share another update in 30 minutes or as soon as this has been fully resolved. 

10:37 PM PST

We've identified the cause of the problem and we are deploying a fix. We'll be back as soon as we have more news or in 30 minutes, whichever is sooner.

10:06 PM PST

There's no additional news to share just yet, but we're working to get things back to normal as quickly as possible. We'll share another update in 30 minutes. 

9:36 PM PST

In addition to trouble with the Threads view, some users may be unable to send messages in specific channels or conversations. We are actively investigating this issue and we'll be back with another update in 30 minutes. 

9:06 PM PST

Unfortunately, some users may be experiencing issues with the Threads view again. We're on the case and working to fully resolve this as fast as we can. We'll provide another update as soon as we have news to share. 

8:28 PM PST

We've deployed a fix and everything should be running smoothly once more. If you're still running into trouble, you may need to refresh the app with Cmd/Ctrl + Shift + R to pick up the change. 

Thank you for bearing with us.

6:18 PM PST

Some users may be experiencing issues sending messages to specific channels or conversations. Additionally, the Threads view may be showing a "Something's fishy!" error message and not loading as expected.

We are investigating and we'll be back with an update as soon as we have more information. We apologize for the disruption to your day.

5:39 PM PST