Your app makes several requests to the conversations.

Slack identifies rate-limit exhaustion through the HTTP status code 429 Too Many Requests. When this occurs, the response includes a Retry-After header containing the number of seconds the application must wait before retrying the rate-limited operation. Slack applies Web API limits primarily on a per-method, per-workspace basis. Consequently, reaching the limit for conversations.list does not necessarily mean that every Web API method for the same workspace has become unavailable. Applications should read Retry-After, wait for the indicated interval, and retry responsibly rather than immediately issuing more requests. Pagination is also important. Slack explicitly notes that methods supporting cursor-based pagination may receive stricter rate treatment when an application attempts to retrieve extensive datasets without using pagination appropriately. A growing workspace therefore makes efficient pagination and caching increasingly important. HTTP 500 generally indicates a server-side failure rather than rate limiting. HTTP 200 can contain method-level errors or warnings but is not Slack's rate-limit signal. A Timeout header is not the prescribed rate-limit response mechanism. This is a core Design for Scale concept: applications must handle API limits predictably as data volume and workspace size increase.