Loading

Smart Alert Catalog: Proactive Services for Slack

Veröffentlichungsdatum: Nov 10, 2026
Beschreibung

Interested in Smart Alerts for other products? Check out the Smart Alert Catalog: Proactive Services for Sales, Service, Agentforce, Data 360, Experience Cloud and Platform.

 

The Signature Success Plan for Slack comes with Proactive Services and Smart Alerts that will notify you in real-time when your Slack organization has platform health degradations, integration errors, or identity provider issues.

 

Here's a list of the current Smart Alerts available through Proactive Services for Slack, including their technical descriptions, business impacts, and the insights you will get from each one.

LimitsErrorsPerformance
Platform Rate Limit
Critical Feature Rate Limit
Platform Error Spike
Critical Feature Errors
SSO Login Failures
 

 

Lösung

Smart Alert Technical Descriptions, Business Impacts, and Insights Delivered

CategoryNameTechnical DescriptionBusiness Impacts & Proactive Insights Delivered
LimitPlatform Rate LimitThis alert monitors rate limit enforcement events, where API requests from an app installed in your organization are rejected with an HTTP 429 response. It fires when a single app and method combination sustains rejections above the threshold configured for your organization, for the configured duration.Rate limit rejections mean active, user-facing failures. Every rejected request is a failed action for one of your users — a message not sent, a workflow not triggered, a search that returns nothing. Sustained rejections indicate an app that is not implementing backoff correctly, and that is actively degrading the Slack experience in your organization. Insights include the app being rejected, the API method, and the number of rejected requests.
LimitCritical Feature Rate LimitThis alert monitors internal rate limiting applied to core Slack features — messaging, search, channels and similar — for your organization. Unlike the Platform Rate Limit alert, which covers rate limiting caused by apps installed in your organization, this alert indicates pressure on Slack's own infrastructure. It is an informational alert.When core features are rate-limited, users may experience slowness or failures on basic Slack operations. This alert exists to give you visibility that Slack is already aware of the degradation, so you do not need to open a case to find out whether it is known. No action is required from your side.
ErrorPlatform Error SpikeThis alert monitors API errors returned to apps installed in your organization, using rate-of-change detection. It fires only when the error count in the current 30-minute window exceeds both an absolute minimum and a multiple of the previous 24-hour average for your organization. Requiring both conditions filters out the steady background level of errors produced by apps that are no longer actively used, so the alert fires only on new breakages.A sudden spike in API errors typically means something broke — an app update introduced a bug, an API was deprecated, or a permission was revoked on an active integration. Without this alert, these issues are usually discovered only when downstream workflows fail or users report problems. Insights include the most frequent error code, the app that produced it, and the API method involved.
ErrorCritical Feature ErrorsThis alert monitors errors on core Slack features using rate-of-change detection together with a cross-organization comparison. It fires when error volume spikes above your organization's normal baseline, and then determines whether the pattern is specific to your organization or also affecting others. The guidance in your case depends on which applies.Critical feature errors mean core Slack operations — messaging, channels, search — are failing for end users. The cross-organization comparison matters because an isolated issue often indicates a configuration problem that can be corrected, while a widespread one means Slack engineering is already aware. Insights include the API methods, the error codes, and how far above your normal baseline the volume is.
ErrorSSO Login FailuresThis 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.

Note: If there is a requirement to disable notifications or to modify proactive monitoring alert thresholds for specific components, please inform the Proactive Monitoring team through the ongoing ProM case. Alternatively, you may contact your Customer Success Manager for assistance.

Salesforce may change the Proactive Monitoring, Smart Alert Catalog from time to time in its sole discretion. SFDC will provide customers with advance notice of any planned downtime.

Nummer des Knowledge-Artikels

005465421

 
Laden
Salesforce Help | Article