{"id":212,"date":"2025-02-27T18:20:04","date_gmt":"2025-02-27T18:20:04","guid":{"rendered":"https:\/\/www.techrepublic.com\/?p=4294053"},"modified":"2025-02-27T18:20:04","modified_gmt":"2025-02-27T18:20:04","slug":"slack-outage-disrupted-work-messaging","status":"publish","type":"post","link":"https:\/\/blog.tecnoartesanos.com\/index.php\/2025\/02\/27\/slack-outage-disrupted-work-messaging\/","title":{"rendered":"Slack Outage Disrupted Work Messaging"},"content":{"rendered":"
<\/div>\n

Slack reported an outage on February 26 and 27, with most features back up by Thursday but some issues with messaging still persisting; in particular, some custom apps and bots did not work as expected. In addition, a problem with Slack Connect meant coworkers might not get notified if someone pinged them with the @ command. According to Downdetector<\/a>, about 3,000 people had reported issues at the peak of the problem.<\/p>\n

As of Thursday morning, Slack said most features had been restored. Users still experiencing trouble were advised to reload Slack (Command + Shift + R  on Mac or Ctrl + Shift + R on Windows or Linux).<\/p>\n

<\/span>Slack team\u2019s response to the outage, including Slack Connect tips<\/span><\/h2>\n

The loss of functionality on Wednesday was \u201c\u200b\u200brelated to Events API and is a symptom of an earlier incident about trouble connecting to or loading Slack,\u201d plus an unrelated problem with Slack Connect causing the lack of notifications, Slack said.<\/p>\n

Our workplace sysadmin team announced problems with Slack<\/a> at around 1:00 p.m. EST on February 26, with some employees being unable to post messages. (My work was not disrupted.)<\/p>\n

SEE: Slack added tools for automatically building workflows<\/a>, including for developers. <\/strong><\/p>\n

By Wednesday evening, Slack\u2019s status site said, \u201cWe\u2019re continuing to diligently work on database shard repair and have made progress on restoring affected replicas, though users may still be experiencing impact.\u201d<\/p>\n

Later that day, Slack personnel were working on \u201cre-processing of the backend job to attempt to serve queued Events API requests.\u201d Slack suggested the following mitigation for users having trouble mentioning others using Slack Connect:<\/p>\n

    \n
  1. Open the Slack desktop app, then click Help in your computer\u2019s top menu bar. (On Windows 10, click the three horizontal lines icon in the top left of the Slack app.)<\/li>\n
  2. Select Troubleshooting.<\/li>\n
  3. Click Clear Cache and restart.<\/li>\n<\/ol>\n

    The Slack team said the cause of the outage was \u201ca symptom of an earlier incident,\u201d and did not specify further.<\/p>\n

    Messages, workflows, threads, and other API-related features were last to come back online.<\/p>\n