Monday August 22, 2022


Some users are encountering a "Reload required" message

Issue Summary:
From August 22, 2022 5:15 PM PDT to August 23, 2022 01:15 AM PDT, some customers experienced a persistent reload prompt when when their user account was converted from a member account to a guest account, even after a reload was completed.

A recent change made to our code resulted in the removal of a mechanism for indicating when a reload dialogue should appear. We have pushed a fix for this problem by reinstating the mechanism to ensure this only occurs for users once.

11:00 AM PST

We've identified the issue and rolled out a fix. Impacted users are asked to reload Slack twice (Cmd/Ctrl + Shift + R).

If you're still experiencing issues after refreshing Slack, please reach out to us.

7:55 AM PST

Our team is investigating this issue but have identified a potential fix. Impacted users are asked to try and reload Slack twice (Cmd/Ctrl + Shift + R) to see if it removes the "Reload Required" message.

Please reach out to us if you are still experiencing issues after trying to refresh Slack.

2:24 AM PST

Some users are having trouble connecting to Slack after receiving a "Reload Required" message. We are currently investigating and will let you know as soon as we know more.

8:29 PM PST

Services affected






Errors with interactive messages

Issue Summary:
From August 19, 2022 11:55 AM PDT to August 22, 2022 2:52 AM PDT some users experienced issues using the buttons on interactive messages.

We traced the issue to a recent code change, which we rolled back, resolving the issue for all impacted users.

10:11 AM PST

We’ve rolled out a fix to resolve this issue, and impacted customers should be able to use the buttons on interactive messages with an attachment once again.

We appreciate your patience while we sorted this out, and apologise for any disruption to your work day.

3:03 AM PST

Some customers may be experiencing issues using the buttons on interactive messages with an attachment.

We’re actively looking into this, and we’ll report back as more information becomes available. We apologise for the disruption.

1:20 AM PST

Services affected