Cohort-specific rate/pagination
Slack Web API conversations.replies rate limit new cohort limit thread backfill 429
Thread backfill takes the old high-rate path and receives repeated 429s.
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: conversations.replies thread crawler exceeds new cohort limit
Likely root cause: Thread backfill takes the old high-rate path and receives repeated 429s.
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
Thread backfill takes the old high-rate path and receives repeated 429s.
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.replies rate limit new cohort limit thread backfill 429
site:docs.slack.dev conversations.replies rate limit 1 request per minute 15 messages
Slack conversations.replies rate limit 1 request per minute 15 messages 2025
https://docs.slack.dev/reference/methods/conversations.replies