Cohort-specific rate/pagination

Slack Web API rate limits conversations.history 1 request per minute Marketplace commercial distribution internal apps

A blanket one-request-per-minute workaround makes internal sync unnecessarily slow.

Slack Web APICollaboration SaaS APICohort-specific rate/paginationslack_rate

Agent Quick Fix

Repair against the current Slack Web API contract, then keep the change narrow and source-backed.

Product: Slack Web API
Current-contract area: Internal customer-built app should not be throttled like commercial distribution
Likely root cause: A blanket one-request-per-minute workaround makes internal sync unnecessarily slow.
Repair direction: Verifier checks backoff, pagination completeness, and installation-aware behavior under the current limits. Verify complete synchronization under each cohort without hard-coding one global throttle.

Symptom

A blanket one-request-per-minute workaround makes internal sync unnecessarily slow.

Why This Happens

The code can work for existing/internal installations yet fail for newly created or unlisted apps; account cohort and current service policy are external.

Common Wrong Fixes

Changing local code without checking the current external contract.
Retrying the same install, build, or API call with no version/source change.
Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

site:docs.slack.dev Web API rate limits Slack internal customer-built app non-Marketplace commercial distribution conversations.history one request per minute
Slack Web API rate limits conversations.history 1 request per minute Marketplace commercial distribution internal apps
Slack Web API rate limits conversations.history 1 request per minute
https://docs.slack.dev/apis/web-api/rate-limits/
https://docs.slack.dev/reference/methods/conversations.history/