We have successfully deployed the fix to production and the issue is resolved.
The Admin SSO and Authentication Configuration page for standalone workspaces should now display the correct settings. If you continue to see outdated information, refresh the SSO Admin page to load the latest changes.
update
We have identified the trigger and developed a fix. We are currently deploying this fix and expect to resolve the issue shortly. We will provide another update once the deployment is complete.
We apologize for the inconvenience.
update
Some workspace admins on standalone (non-Enterprise Grid) workspaces may be experiencing an issue where the SSO and authentication configuration page does not display current settings as expected. Admins may see a blank value for the "Require SSO authentication for" field on the admin SSO settings page, which does not accurately reflect the actual backend configuration — SSO settings remain intact and in effect.
We are actively investigating this issue and will provide an update as soon as we have more information to share. We apologize for the inconvenience.
This issue is now resolved for all users.
We apologize for any disruptions to your day.
update
Some users may be experiencing issues performing certain actions in Slack, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.
Trouble submitting workflow forms with file attachments on Android.
This issue has been resolved. Android users who were experiencing issues submitting workflow forms containing a required file upload field can now do so successfully. A fix was delivered via a new update to the Slack Android app. Users who are still experiencing this issue should update the Slack app from the Google Play Store to resolve it. No other action is required.
We apologize for the inconvenience and thank you for your patience.
update
We continue to monitor the rollout of the new version of Slack for Android. We'll provide another update when we have further information to share. Thank you for your continued patience.
update
The rollout of the new version of the Slack Android app is ongoing and may take up to several days to fully complete. We continue to monitor the rollout and will provide another update when we have more information to share. Thank you for your patience with us while we work through this.
update
A fix for this issue has been delivered in a new version of the Slack Android app, and rollout has now begun. Android users will start seeing the updated app version become available in the Google Play Store as the rollout progresses.
Once updated, users who were experiencing issues submitting workflow forms containing a required file upload field will be able to do so successfully.
We will continue to monitor the rollout and provide another update as additional information becomes available.
update
We have identified the cause of this issue and confirmed it affects a small subset of users on a single version of the Slack Android app. Users on other Android versions, iOS, and web are not affected. A fix is already available and will begin rolling out to Android users tomorrow. We will provide an update as soon as additional information becomes available.
update
We are aware that some users on the Slack Android app are unable to submit workflow forms that contain a required file upload field. After a file is selected, the Submit button becomes disabled and the form cannot be completed. Users on Slack for iOS and Slack for web are not affected. We are actively investigating the issue and working to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.
We've validated that the fix resolved the issue and child windows are now displaying content as expected.
You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.
update
We’ve deployed a fix and are now performing validations. We'll provide an update in 30 minutes or sooner if additional information becomes available.
update
We're aware of an issue affecting the Slack desktop app. Users may find that content in child windows, such as channels or documents opened in a separate window, displays at reduced height. We’ve identified the technical trigger and are deploying a fix.
We'll provide an update in 30 minutes or sooner if additional information becomes available.
We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users.
We apologize for any inconvenience this may have caused.
update
We’re continuing to investigate the issues with the Slack Gmail add-on and are actively working on a fix to resolve the issue. There’s no new information to share at this time, but we’ll provide an update as soon as we have more details on implementing the fix.
We apologize for any inconvenience this issue is causing for users.
update
We’re actively working on the fix to resolve the issue. We estimate this will take approximately four hours or more to complete, and validate the fix, before it can be deployed. As such, the next status update will be once the fix has been completed and validated, or we have new information to share. We apologize for any inconvenience this issue is causing for users.
update
We continue to investigate the issue impacting Slack Gmail add-ons. We've identified the cause and our teams are working on a fix to resolve the issue as soon as possible.
We’ll provide an update once additional information becomes available.
update
We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
update
We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
update
We’re still actively investigating the issue impacting the Slack Gmail add-on. We are working to identify the cause, and no workaround is currently available. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
update
We're aware of an issue impacting the Slack Gmail add-on integration. As a result, users are unable to interact with the add-on and may encounter a “Something went wrong when executing the add-on. For help, contact the add-on developer” error message when attempting to use it. We are investigating the cause of this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.
We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding.
We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users.
If you're still experiencing any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and appreciate your patience.
update
We've deployed a fix for the issue and are monitoring to confirm that the issue has been resolved.
We'll provide another update as soon as more information becomes available.
update
We’ve identified the cause of the issue and we’re validating a fix to ensure it fully resolves the issue before we deploy it.
We'll provide further update as soon as more information becomes available.
update
We’re working to reproduce the issue. This will help us identify the underlying cause and provide a resolution.
We'll provide further update as soon as more information becomes available.
update
We've received reports that a subset of users may continue to experience issues when attempting to add multiple users to channels using email addresses. These users may encounter a "Multiple matches" error, preventing the intended user from being identified and added to the channel.
We’re actively investigating these reports to determine whether additional remediation is required. We'll provide further updates as more information becomes available.
update
This issue is now resolved for all users.
Current status and recent actions taken: We identified the trigger for this issue and a fix was deployed. After a period of monitoring, we have concluded that there is no further impact to users.
Previous impact to end users: Some users may have experienced issues when attempting to add multiple users to channels and received an error indicating a failure to identify team members. This could have caused subsequent workflows not to trigger.
Required resolution steps: No further action is necessary.
Thanks for sticking with us as we resolved this. We apologize for any disruptions to your day.
update
Our work on this issue is still ongoing.
Current status and actions being taken: We have identified the trigger for this issue and a fix is in the process of deploying. The progress is being monitored and we’ll provide an update as soon as the fix is completely deployed and verified.
We'll be back with another update once we have news to share.
update
Some users may experience issues when attempting to add multiple users to channels. Multiple matches error may appear along with a failure to identify team members. This may cause subsequent workflows not to trigger. We're investigating and will let you know as soon as we know more.
The issue affecting SMS-based two-factor authentication for users in EMEA has been resolved, and all services are now functioning as expected. We have adjusted configuration settings to restore normal service and will continue to monitor the situation to ensure stability.
We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
update
Some users in EMEA may be failing to receive 2FA codes via SMS when logging into Slack. We are investigating the trigger and working to resolve this incident as quickly as possible.
We will provide another update in 30 minutes or sooner as we have more details to share.
Administrators may experience errors in member management.
The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved.
Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces.
Workspace Admins should now be able to add new members via the Manage Members admin page. A page refresh may be required.
We apologize for the disruption to your work.
update
We have identified the cause of the issue preventing some workspace admins from adding new members via the Admin page as a recent change and are in the process of rolling back this change.
Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace.
Known workaround: Inviting members via the Slack client workspace menu (workspace name → Invite people to workspace) is currently working as expected.
We'll provide an update within 30 minutes or sooner if additional information becomes available.
update
We're looking into an issue where some users may be unable to add new members, send invites, or run macros on their workspaces. We're on the case and will provide another update as soon as we have more details to share. We apologize for any disruption to your work.
Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace.
We'll provide an update within 30 minutes or sooner if additional information becomes available.
update
We're investigating a new incident.
Current impact to end users: Some administrators may be experiencing errors managing members.
We'll provide an update within 30 minutes including further details on current actions being taken.
This issue is now resolved for all users.
Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.
We apologize for any disruptions to your day.
update
Our work on this issue is still ongoing.
Current status and actions being taken: we're investigating an issue where some Slack users are experiencing thread loading, client booting, and message delivery failures. We've identified several potential contributing factors and are working to confirm the root cause. Further updates will be shared as the investigation continues.
We'll provide another update in 30 minutes until the impact is resolved for all users.
update
We're investigating a new incident.
Current impact to end users: Some users may be experiencing trouble loading or connecting to Slack. We're on the case.
We'll provide an update within 30 minutes including further details on current actions being taken.
Legacy Incident Archive
40 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
Incident: Users may experience delays due to increased load on bychan keyspace affecting system performance
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: We've completed rolling back the change to address the issue impacting core Slack functionality, including launching Slack, sending messages, loading threads, and other related actions. Scope: All Slack enterprise customers.Previous impact to end users: Users experienced issues with channel-related operations, including delays or failures when loading channels or retrieving channe...
Incident: Trouble Sending Messages
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. Users should no longer experience any issues when sending messages. Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced...
Incident: Trouble with Slackbot and AI-powered features
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. This incident is now resolved and users should no longer experience any issues with Slackbot, AI Features, or workflows.We apologize for any disruptions to your day.
Incident: Slackbot button in the top navigation is disappearing
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: We've completed deploying the fix to address the issue affecting the Slackbot button in the top navigation bar. The Slackbot button is now working as expected. Scope: The issue was introduced for any users on build 121247.Previous impact to end users: The Slackbot button in the top navigation bar may not have been visible to users.Required resolution steps: Users who are stil...
March 2026
Incident: Issue with Sending and Receiving Messages
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Following a period of monitoring, our engineering team called this incident resolved as of 01:10 UTC, March 30. We apologize for any inconvenience this issue has caused to users.
Incident: Issues while sending messages and loading message history is impacting some users
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: We identified a paused job that may have been contributing to the high utilization. This was unpaused, which restored resource availability.Scope: This only affected a small subset of users.Previous impact to end users: Some users may have experienced issues while sending messages and loading message history in Slack between 20:14 PDT and 22:14 PDT.We apologize for any disruptions to yo...
Incident: Trouble connecting to Slack
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Intermittent errors when sending messages have been resolved. Additionally, some customers may see inaccurate notification badge counts which can be resolved with a hard reload to clear temporary local cache. Apologies for the trouble today and thank you for your patience.
Incident: Authorization Failure Errors Connecting to the Slack MCP Sever
majorSource not attested
Last archived state: investigating
View archived record details
investigating
We have resolved the issue that was causing users to experience authorization failures when connecting certain third-party integrations to Slack.We apologize for any inconvenience this may have caused and thank you for your patience.
This issue is now resolved for all users.Current status and recent actions taken: We identified the cause as a login routing component that had incorrect entries, which prevented users from being directed to their workspace correctly. A fix has been deployed to address this issue. Previous impact to end users: Users attempting to log in via SSO may have encountered errors requiring them to refresh their browser multiple times before successfully accessing...
Incident: Issues with App Mentions, Grid Migrations, and Notifications
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: The issue is now resolved, and users should no longer be experiencing any trouble with when using app mentions, migrations, and push notifications. Enterprise Migrations should also be completing as expected.Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Developers may have experienced issues in ...
