Slack

Beginning at 2:03 PM PDT on August 25, 2025 until 2:27 PM PDT, some users may have experienced trouble loading threads in Slack, resulting in a "Something's fishy!" message.A backend capacity change unexpectedly caused a subset of databases to enter a bad state preventing traffic related to loading thread content from being served properly. The affected databases would accept new entries, but were temporarily unable to read thread content, resulting in errors.We reversed the changes that caused ...

Starting on August 27, 2025 at around 4:41 PM PDT until 6:31 PM PDT on August 28, 2025, some apps/integrations were showing a "Can't fully display message" error in Slack for users attempting to select options within a dropdown menu element.A backend change was made to the structure of the "external_select" block in Slack Block Kit, causing improper value conversions, leading to the errors. We reverted the change, resolving the issue for all affected users and integrations.

Beginning around 7:00 AM PDT to 11:42 AM PDT on August 28, 2025, some users were experiencing trouble with user statuses in Slack. These users would incorrectly appear as "Away" despite being active in Slack.A backend server responsible for managing user presence (if a user is active or away in Slack) experienced an influx of errors that disrupted the way these user events were processed. We identified the problematic server and restarted it's processes, resolving the issue for all affected user...

Beginning around 1:47 PM PDT until around 10:00 PM PDT on August 29, 2025, some users experienced an issue when attempting to install a custom app/integration in Slack. When navigating through the app authorization pages, the "Allow" button would show disabled, preventing users from completing the install.A backend logic change unexpectedly introduced some inconsistent dependencies related to how the button was being rendered for users. We investigated these dependencies and reverted the problem...

Starting at around 7:30 PM PDT on August 31, 2025, until around 5:35 AM PDT on September 1, 2025, some users were unable to authenticate their Outlook account when using the Microsoft Outlook Email steps in Workflow Builder, specifically the "Send an email" step. This may have presented as a "Something went wrong" page with an "access_token_exchange_failed" error.A backend authentication configuration was attempting to use incorrect credentials when initiating the OAuth flow, which resulted in t...

On September 3, 2025, between 3:00 PM and 5:40 PM PDT, some iOS users running Slack app version 25.09.10 saw a "Jailbroken devices can't use Slack" error message.A recently enabled toggle for jailbreak protection (which prevents apps from running on devices with removed software restrictions) unexpectedly introduced a backend check that incorrectly identified the installed iOS version. This caused some users' devices to be improperly flagged, preventing them from using or opening the app. We pro...

From 1:50 PM PDT on September 9, 2025, until 7:46 AM PDT on September 12, 2025, some users had an issue where the Activity tab in Slack would show an unread count badge even when there was no new activity.This was caused by a recent backend change that unintentionally prevented unread badges from clearing. We've rolled back the problematic code and pushed out a fix. All affected users should no longer run into this issue. Should any users still be experiencing this, please hard refresh your clie...

From September 15, 2025, at around 11:00 PM PDT, through September 18, 2025, at around 9:30 PM PDT, some users may have experienced an issue with unread items in their Activity view. Specifically, the badge indicating unread items would not disappear even after the activity was read.We traced the issue back to a recent change in how the Slack client handles the item row within the Activity view, which introduced this bug. We also determined this was related to a similar badging issue that occurr...

Starting at around 10:42 AM PDT, until around 1:25 PM PDT on September 17, 2025, some users that were logged into their Slack app were unable to access https://slack.com/, instead they were receiving an error message. We identified a recent code change to the logged-in user experience on this page. The change caused the page to fetch an incorrect value for the user, which introduced the error. We reverted the change, resolving the issue for all affected users.

Starting around 7:30 PM PDT until approximately 10:18 PM PDT on September 19, 2025, some users on Android were experiencing app crashes when attempting to launch Slack.At approximately 5:40 PM PDT on September 20, 2025, we received several reports of Android users experiencing this issue and began our incident response process.We traced the issue back to a specific app version, 25.09.40, where users would encounter a crash upon startup. This version contained a bug related to improperly loading ...

Starting around 5:00 PM PDT on September 22, 2025 until around 5:52 AM PDT on September 23, 2025, some users on desktop and browser version of Slack were unable to update their user profiles, including their profile photo, name pronunciation, and other link buttons. The options would present as grayed out.A bug related to the profile sidebar originating from an improper backend condition check within the app caused the options to render as disabled. We corrected the logic, resolving the issue fo...

Starting around 12:15 PM PDT until around 4:10 PM PDT on September 23, 2025, some users experienced errors and latency when attempting to query items using the AI search feature in Slack.A backend search system encountered an unexpected spike in processing times, resulting in downstream latency and timeouts when users would attempt to use Slack AI search. We identified the cause of the unexpected processing spike and introduced additional load handling measures to resolve the issue for all users...

Starting around 2:00 PM PDT until around 5:15 PM PDT on September 26, 2025, some users experienced issues with custom internal-built integrations in Slack. Affected apps would return a "rate_limited" error for conversation related APIs such as "conversations.replies" or "conversations.history".We traced this back to a recent change related to AI-search custom app functionality that inadvertently introduced a rate limiting bug for all custom built apps. This bug was connected to a mis-matched con...

Starting around 8:30 AM PDT until around 9:18 AM PDT on October 15, 2025, some users may have experienced issues querying searches in Slack. Searching for messages, files, people, channels, and internal or external users were returning unexpected errors or failing. Some admin dashboards that relied on search functionality may have also experienced issues loading.A backend system responsible for processing search queries experienced a large influx of traffic, causing the spike in errors. We ident...

Between approximately 9:30 AM and 10:14 AM PDT on October 15, 2025, some users experienced slowness or errors when loading messages and threads in Slack.The issue was caused by an unexpected spike in traffic on a specific database, triggered by an ongoing backend job. We We implemented measures to process any related backlog and immediately paused the problematic job, which resolved the issue.

Starting around 12:13 PM PDT on October 19, 2025, and lasting until around 3:51 PM PDT on October 20, 2025, a significant number of users may have experienced trouble with various features in Slack. This included difficulty loading or editing canvases, starting or ending huddles, connecting to or loading the client, sending messages, loading channels and threads, or using integrations that utilize the Events API. Additionally, some workflows may have triggered multiple times.This issue was the r...

Our mitigation efforts have resolved the majority of stuck huddles. Newly started huddles are working as expected, and we are continuing to clean up the small number of remaining huddles that might be in a stuck state.The issue is resolved. If you are still encountering stuck huddles, please write to feedback@slack.com. We apologize for any inconvenience.

Starting at 8:15 PM PDT on October 21, 2025, until around 1:00 AM PDT on October 22, 2025, some users may have experienced partial search results when querying items in Slack.A backend change unexpectedly initiated a restart job for some services responsible for handling searches. These jobs inadvertently caused the search processing capacity to become temporarily overwhelmed, creating a large backlog of queries. To help mitigate this, we performed a restart of the relevant indexing processes, w...

Between 3:00 AM PDT and 11:00 PM PDT on October 22, 2025, some Slack users experienced trouble with searching. Search results for these users were either missing or only returning partially.A backend indexing job, which processes search results, experienced a backlog of errors. The errors required a large number of job retries, causing the partial results. We implemented a fix by optimizing the retry handling logic, resolving the issue for all affected users.