Cohort-specific rate/pagination
Slack Web API rate limits new commercially distributed apps existing apps grandfathered May 29 2025 conversations.history conversations.replies
Support cannot reproduce because the vendor's long-lived workspace is grandfathered.
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: Existing installation works while net-new installation fails
Likely root cause: Support cannot reproduce because the vendor's long-lived workspace is grandfathered.
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
Support cannot reproduce because the vendor's long-lived workspace is grandfathered.
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 rate limits new commercially distributed apps existing apps grandfathered May 29 2025 conversations.history conversations.replies
site:docs.slack.dev Web API rate limits commercially distributed apps new rate limits May 2025 Slack
Slack API rate limits commercially distributed apps May 29 2025 conversations.history conversations.replies
https://docs.slack.dev/apis/web-api/rate-limits/