Wednesday August 14, 2019

Incident

Slash commands are failing for some apps

Issue Summary:

At 3:47 p.m. PDT on August 14, 2019, we started receiving reports that some app slash commands were suddenly failing. This was due to a code deploy earlier that day which prevented these slash commands from responding as expected. We reverted the changes to restore functionality, and the issue was resolved at 5:24 p.m. PDT.

7:33 PM PST

We have resolved the slash command problem, and all slash commands should be working smoothly once again. We're very sorry for the disruption. Thank you for bearing with us.

5:45 PM PST

Some people may be experiencing issues when using slash commands. Thank you for your patience as we look into this, and we'll let you know once we have an update to share.

4:09 PM PST

Services affected

Apps/Integrations/APIs

Status

Resolved

Incident

Issues with search for some customers

Issue Summary:

On August 14, 2019 at 1:30 p.m. PDT, we kicked off a new process for our search data which caused unexpected stress across our search systems. In order to rectify the issues we paused specific functions in search, which caused failed searches for all users.

Our team quickly narrowed down the issue and managed the stress of our search servers until we were confident our servers were not being overwhelmed further. We called an All Clear at 8:06 p.m. PDT.

7:30 PM PST

Full search functionality has been restored and everything should be back to normal. We're very sorry for the disruption. We'll report back with an Issue Summary.

8:14 PM PST

We're still all hands on deck as we work to set search to rights. Thank you for your patience.

7:36 PM PST

No additional news to share just yet. We're focused on getting things back to normal as quickly as we can.

7:06 PM PST

We're still working to restore full functionality, and we'll be back with more information soon.

6:33 PM PST

We're seeing some improvements, but we're not out of the woods quite yet. We're actively working to restore full search functionality, and we'll share more news shortly.

5:58 PM PST

We're still tackling the search issues, but we don't have any additional information just yet. Thank you for bearing with us.

5:25 PM PST

We are continuing to look into the issues with search at this time. If you are affected, we do apologize for the trouble. We will be back again soon with a further update.

4:54 PM PST

We are investigating reports of searches failing for some customers. We will report back here once we have more information. If you're affected, we truly apologize for the disruption.

4:20 PM PST

Services affected

Search

Status

Resolved