On January 6, from 3:23 AM PST to 4:50 PM PST scheduled workflows were not triggering correctly for some users.We identified that a recent update to our internal infrastructure had added unexpected load to the backend database that processes workflow triggers, which was causing scheduled workflows to fail.To mitigate further issues, we cleared these failed triggers from our systems. However, this inadvertently caused some workflows to re-trigger outside their scheduled time on customer’s workspaces.Once these failed triggers had been fully removed, we confirmed that scheduled workflows were working as expected again.

Beginning around November 22, 2024 until January 16, 2025, some users on the desktop versions of Slack experienced unexpected behavior with sidebar bolding & badging for direct messages (DMs), group DMs, and channels. This caused users to miss unread messages within these conversations.We initially were tracking reports from affected users, but on January 6, 2025, we noticed an unexpected increase of reports causing us to initiate our incident response processes.As an initial fix, we rolled out a change to the backend logic to correct the timestamp and store correct values so the client triggered the appropriate badging & bolding notifications. While this fix resolved the initial badging & bolding behavior, it unexpectedly caused an issue with badging counts, resulting in displaying an incorrect number of unread messages as well as not marking a channels read state correctly. We promptly reversed this change to avoid further impact.We continued our investigation efforts and discovered an additional cause within the backend logic checks related to how a message is routed to the client. This check ensures the client is fetching the proper information that triggers the notification badging & bolding. We adjusted the problematic logic within this check to ensure the proper data is fetched when triggering a notification, resolving the issue for affected users.Throughout this incident, we adjusted our strategy on how to best handle incoming reports from affected users, which impacted updates on our status site. As more users reported experiencing this issue, we then resumed our status site updates.We apologize for any confusion and disruptions to your work day and appreciate your patience as we worked to resolve this issue for all affected users.

On January 6, 2025 from 12:14 AM PST to 11:09 AM PST, some customers were unable to switch between workspaces on desktop.We identified that an error had been introduced via a routine code change that prevented an upgrade prompt from closing as expected. As the upgrade modal retained focus while open, this prevented users with a workspace on the free plan from switching between workspaces.We reverted the code change and the issue was resolved for all impacted users.

On January 13, 2025 from 4:45 PM PST to 5:05 PM PST, users may have experienced brief issues with Slack, including connecting to Slack, sending and loading messages and threads, and running workflows.We made a planned changed to part of our infrastructure that inadvertently caused a problem on one of our database clusters, resulting in failures across a number of our API endpoints. Our automatic recovery systems stepped in and restarted the database cluster, restoring API success rates and resolving the issue for all impacted users.

From 6:00 AM PST to 11:30 AM PST on January 16, 2025, some users on Enterprise Key Management (EKM) enabled workspaces may have experienced intermittent errors while using Slack.An issue with part of our infrastructure caused a spike in errors on the EKM server cluster, resulting in inconsistent performance across Slack features including workflows, files, message posting, and huddles.We redistributed incoming traffic to unaffected server clusters, restoring normal service for all impacted users.