Loading

Slack Proactive Monitoring Alert: Platform Rate Limit

Data pubblicazione: Nov 10, 2026
Descrizione

This 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.

Risoluzione

1. Confirm which app is being rejected, and whether it is respecting Slack's backoff headers

Your case names the App ID, the API method, and the number of rejected requests.
When Slack rejects a request with HTTP 429, the response includes a Retry-After header telling the app how long to wait before trying again. An app that keeps sending at the same rate is not reading that header, which is why the rejections persist rather than clearing on their own.

To put a name to an App ID, go to Organization settings → Integrations → Installed apps and search the ID. The app's page shows its name, every workspace it is installed in, when it was installed and by whom, and its Source:

  • Slack Marketplace — reviewed by Slack and listed publicly
  • Internal — built inside your organization
  • Distributed — a third-party app that has not been submitted for Marketplace review

You can export your full app inventory as CSV from the same page.

2. Contact the app developer to implement proper retry logic with exponential backoff

Who to contact follows from the Source value above. For an Internal app, its app managers and collaborators are your contacts. For a Marketplace app, the developer's support contact is on its Marketplace listing. For a Distributed app, contact the vendor directly.
Three things resolve nearly all sustained rate limiting, and are worth passing on specifically:

  • Honor Retry-After. On a 429, wait the interval Slack specifies, and back off exponentially if limiting continues. Retrying immediately makes it worse.
  • Cache rather than re-fetch. Channel and user metadata rarely changes between calls. A large share of rate limit problems is an app repeatedly reading data it already holds.
  • Account for per-workspace scoping. Limits apply per app, per workspace, per method, so an app installed across many workspaces has a separate budget in each. A fix needs to apply everywhere it is installed.

3. Consider temporarily restricting the app if it continues to misbehave

Turn off access while a fix is prepared. In Installed apps, select the app and set Who can use this app? to No one. Your users can no longer run its slash commands, use its shortcuts, press its buttons or open its dialogs, and its shortcuts are removed from the shortcuts list. The installation, its tokens, its permissions and its channel memberships all remain intact, and setting access back to Everyone restores it immediately with no reinstall or re-authorization. Note that this stops people using the app — it does not stop the app's own background requests, so rejections may continue until the developer ships a fix.

4. See Slack's rate limit documentation for implementation guidance

Slack API rate limits — written for developers, so this is the link to forward to whoever maintains the app.

Numero articolo Knowledge

005462390

 
Caricamento
Salesforce Help | Article