-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
request recharge time is too long #250
Comments
I want to reduce this delay but I can't find such a setting. |
Hey, thanks for opening an issue. When encountering "HTTP Error 429" or "you've been posting too frequently, and can't make another post right now" the bot adds 5 minutes to the length of the request (basically preventing the accounts from being used for another 5 minutes). I'm not exactly sure why you are getting a 40 minute cooldown when you have both cooldowns disabled in the config. How many comments failed in that request from your first screenshot? Knowing that could maybe answer that theory. |
Depending on which errors you encountered my theory might make sense. |
This has been fixed, the 5 min IP cooldown penalty will only be applied once to a request instead of stacking incorrectly. The fix will be included in Version 2.15.3. I'll leave this issue open until the update is out on the master branch. Edit: I could maybe also add an advancedconfig setting to disable this penalty, although it would not make much sense as the accounts will get reused which might extend the IP cooldown further. |
Version 2.15.3 is now out which fixes the issue. |
Question or issue you are experiencing
Please explain your question here. If you've got an error or something else related, then please include it here as well.
hi, when I use a command, sometimes I encounter failed, and when I need an even amount I want to reuse it, but I don't understand why the program asks to wait such a long time
my config:
Additional information
Please add any other information here, if you have some.
The text was updated successfully, but these errors were encountered: