We've resolved the issue and users can now use the Chat feature on the Slack Help Center. We performed a configuration change, which brought the feature back online and have validated that it's functioning as expected.

We apologize for how this incident may have affected you and your business.

Additional Slack engineers have been engaged and are investigating this issue.

As a workaround, if users require support, they can use the ‘Send us a Message’ functionality on the Slack Help Center page here: https://slack.com/intl/en-gb/help/requests/new . A member of the Slack team will then be in touch.

We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

We're aware of an issue affecting users ability to reach our Slack Support team via the Chat functionality on the Slack Help page. Users will be unable to click on the ‘Chat’ option and will see a ‘Chat is temporarily unavailable. Please send us a message or check back later’ error message.

We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.