This alert monitors SSO and SAML authentication failures for your organization using rate-of-change detection. It fires when failures in the current 30-minute window exceed both an absolute minimum and a multiple of the previous 24-hour average, or when the recorded reason indicates your SSO configuration could not be found at all. It is scoped to the failure reasons an administrator can act on, rather than to individual sign-in problems such as a mistyped password.
SSO failures mean users cannot sign in. Unlike a mistyped password, sustained SSO failures almost always indicate a configuration problem — an expired certificate, changed metadata, a wrong issuer, or an attribute mapping error — that an administrator can correct once they know about it. Without this alert, the breakage is usually discovered only when users report being locked out.
Your settings are at:
The quickest way to see what is actually failing is Test Configuration on that page. It performs a real sign-in round trip to your identity provider and returns the specific error encountered, which is the only place a precise SAML error is shown directly to an administrator — Slack's access logs record successful sign-ins rather than failed ones.
Then check each value Slack holds:
Two things to know before you save anything. Saving any modified SAML field immediately re-authenticates you through your identity provider, so an incorrect value can sign you out of the page you are working on — keep a second Owner session available. And deleting an SSO configuration signs out everyone currently authenticated through that identity provider.
Your case names the failure reason recorded most often during the window, which narrows the list above considerably.
If it is a configuration-not-found error, the failure is happening before your identity provider is ever contacted — Slack could not locate an active SSO configuration to send the request to. Confirm on the settings page above that your configuration is still present, active, and correctly saved.
Reply to your case quoting the failure reason from the alert and noting whether Test Configuration passes. That pairing is normally enough for us to identify the cause quickly.
If no Owner is able to sign in at all, say so in your reply. Workspace Owners and Org Owners can normally sign in with an email address and password rather than SSO, which is how you would reach your settings during an outage — but if your organization has configured SSO to be required for Owners as well, that path is closed and we will need to help you regain access.
Slack can only count failures it observes. If your identity provider displays its own error page rather than returning the user to Slack, Slack never sees that failure. Treat the figure in your case as "at least this many," and expect that the number of affected users may be higher.
005462487

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.