docs(skills): add Slack rate limit guidance - #150
Merged
Conversation
An agent recently ran 15 parallel channel-scraping workflows at a 20-message page size and got stuck for 4 hours behind Slack rate limits. Document the actual limits, serial-only querying, large page sizes, and reassessing instead of retrying into repeated 429s. Co-authored-by: Orca <help@stably.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
conversations.historyto Tier 1 / 15 messages per call for non-Marketplace apps)jqinstead of loading the whole fileWhy
An agent recently scraped 15 channels via parallel agent workflows at only 20 messages per call, and got stuck ~4 hours behind rate limits across all 15 agents, running up a large bill for no additional data.
Test plan
Made with Orca 🐋