Did you think that your coworkers were ignoring you yesterday?
Well, they might have been - but the issue may also have been caused by problems with Slack's messaging service. From 3:54pm GMT+1 on the 29th of July, Slack announced that it was "receiving reports" about issues with messages that didn't send or load properly on the app.
According to the status page, users were having a hard time sending messages to their peers and receiving content in return. This isn't the first outage that Slack has had this year or even this summer for that matter. Slack also experienced a worldwide outage at the end of June too. That's not a fantastic sign for a tool that millions of people rely on to get work done.
To reassure the countless employees who stormed Twitter, complaining that their bosses would think that they were "slacking off," Slack's support team jumped onto the case as quickly as they could, handling errors with:
- APIs, apps, and integrations
- Network connections
- Messages not sending or opening
- Workspaces not opening
- Message history not loading
Is Slack Back in Action?
By 4:54 pm GMT+1, Slack had announced that users once again have the "all clear" to use their Slack channels without issue. According to the engineering team, the problem came from a change within the software made on the 29th of July, which "inadvertently" led to a handful of performance issues, including issues with messages that failed to send.
Aside from missing messages, Slack also had reports from people who were unable to load their Slack workspaces at all. Although the issue was entirely resolved within an hour or so, it's also just the latest in a series of problems with the Slack user experience of late.
