Monday May 6, 2019

Incident

Issues with iOS message history in new channels

Issue Summary:

On April 23, 2019, an update was rolled out to our iOS app, which contained a bug that caused some recent channel message history to disappear. We've fixed the bug and submitted an updated app version to the App Store. The updated app version will start rolling out today.

11:48 PM PST

We've honed in on the issues with iOS message history and submitted a fix which will be made available through an update to the App Store in the next few days. If you're still seeing any trouble with viewing channel history after the update, please write into feedback@slack.com.

10:28 AM PST

Customers using the iOS app may be unable to view the full message history of recently created channels. We're on the case, and we apologize for the disruption as we look in to this.

12:51 AM PST

Services affected

Messaging

Status

Resolved

Incident

Issues setting up new instances of the Twitter integration

Issue Summary:

On May 6, 2019 at 10:06 a.m. PDT, we deactivated an old configuration that used to handle our Twitter message services, which caused new attempts to create Twitter integrations to fail. The root cause of the problem was found at 7:21 p.m. PDT and we restored the service without any loss of Twitter messages or subscriptions. The all clear was called at 7:27 p.m. PDT.

11:46 PM PST

We have resolved the problem with setting up new instances of the Twitter integration, and it should all be running smoothly now. Apologies again for the trouble.

If you have any further hassles, please let us know at feedback@slack.com.

7:35 PM PST

Customers are unable to set up new instances of the Twitter integration at the moment. We've got all hands on deck as we investigate, and we're very sorry for the disruption.

6:44 PM PST

Services affected

Apps/Integrations/APIs

Status

Resolved

Incident

Trouble using slash commands

Issue Summary:

On May 6, 2019 at 3:04 p.m. PDT, we received a report that slash commands were failing. An internal investigation was launched and we determined that a recent code change had introduced a bug. We made the required code change, which allowed customers to use all slash commands again. The all clear was called at 5:32 p.m. PDT.

11:45 PM PST

Everyone should be able to use slash commands as expected once again. Thank you for bearing with us while we got to the bottom of this. We're very sorry for the trouble.

5:36 PM PST

Some folks may be unable to use slash commands. We’re currently investigating and will let you know as soon as we have more news to share. We apologize for any disruption to your workflow.

4:38 PM PST

Services affected

Messaging

Status

Resolved