Cohort-specific rate/pagination
Slack Web API conversations.history rate limit new apps 1 request per minute non Marketplace commercially distributed May 29 2025
History sync works for an old installation but returns 429 almost immediately for a new customer.
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: New unlisted Slack app hits 1 request/minute on conversations.history
Likely root cause: History sync works for an old installation but returns 429 almost immediately for a new customer.
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
History sync works for an old installation but returns 429 almost immediately for a new customer.
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.
Slack Web API conversations.history rate limit new apps 1 request per minute non Marketplace commercially distributed May 29 2025
site:docs.slack.dev conversations.history rate limit 1 request per minute May 29 2025 Slack
Slack conversations.history 1 request per minute limit new app
https://docs.slack.dev/reference/methods/conversations.history