Work message interrupted by the interruption of the slack


Slack reported an interruption on February 26 and 27, with most of the characteristics again for Thursday, but some problems with messages still persist; In particular, some custom applications and bots did not work as expected. In addition, a problem with Slack Connect meant that co -workers may not be notified if someone made them do with the command @. According to Downetector, some 3,000 people had reported problems in the peak of the problem.

Until Thursday morning, Slack said most of the characteristics had been restored. Users were advised to experience problems that would recharge Slack (Command + Shift + R in Mac or Ctrl + Shift + R in Windows or Linux).

Slack's interruption team response, including Slack Connect's tips

The loss of functionality on Wednesday was “related to the API of the events and is a symptom of an anterior incident on problems to connect or load Slack”, plus a problem not related to Slack Connect causing the lack of notifications, Slack said.

Our Sysadmin team in the workplace announced problems with Slack around 1:00 pm Est of February 26, and some employees cannot publish messages. (My work was not interrupted).

See: Slack added tools to build automatically workflows, including developers.

For Wednesday night, the Slack status site said: “We continue to work diligently on the repair of database fragments and have progressed in the restoration of affected aftershocks, although users may still be experiencing impact.”

Later that day, Slack's staff was working on “re -processing Backend's work to try to meet the API applications of tail events.” Slack suggested the following mitigation for users who have problems mentioning others who use Slack Connect:

  1. Open the Slack Desktop application, then click Help in the upper menu bar of your computer. (In Windows 10, click on the three horizontal line icon in the upper left of the Slack application).
  2. Select problem solving.
  3. Click Delete cache and restart.

Slack's team said that the cause of the interruption was “a symptom of an anterior incident” and did not specify more.

The messages, workflows, threads and other characteristics related to the API were the last to be online again.

Past interruptions and Slack's place in the market

Slack has not had an important interruption like this since July 2023. Before that, the service fell several times in 2022 and in January 2021.

Slack is an important partner in the generative effort of the Salesforce generation.

Competitors to lazy include Microsoft, Google Chat and Bumble teams.

scroll to top