-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hitting 429 on a large channel with files #12
Comments
I'm also getting this error when I'm getting to 1800 messages on a channel I'm trying to dump. It would be nice if it could write whatever it had to a file instead of just exiting. By the way I tried changing the tier values & recompiling, but even at 1/10/25/50 (tier1/tier2/tier3/tier4 values) it still throws the same error "slack rate limit exceeded, retry after 1s" after 1800 messages. It's interesting that a 429 seems to get triggered after the same amount of messages, regardless of the timing. I guess the "1s" message is coming from the slack-go library? The https://api.slack.com/docs/rate-limits#rate-limits__responding-to-rate-limiting-conditions implies it would normally be asking for a retry after 30 seconds. |
Hey @foucist thanks for confirming, yes, this message is from the slack library. It's interesting that it hits the rate limit after 1800 messages square.
Would you be able to check, if you compile the branch "rate-limit" would it be able to complete the download of that channel that currently fails for you? That would be great help in confirming this. |
Telegram channel:
We should either die with error or retry, and we do neither.
Follow up:
The text was updated successfully, but these errors were encountered: