You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't send comment replies - have to wait 10 minutes
So whenever I run my app locally, this rate limit thing never was an issue, I could send comments literally every second, mind you that the bot reddit account is fairly new - around 5 days.
I decided that its ready to deploy on heroku, so I did that, it works every now and then, but the thing is, it gives an error. Only gives it on heroku, not locally.
To Reproduce
Unhandled rejection Error: RATELIMIT,Looks like you've been doing that a lot. Take a break for 9 minutes before trying again.,ratelimit
Expected behavior
I actually am confused why this happens, im not sure if that's because of my config or heroku itself? because as I said, this was not the case when I run my bot locally
System Configuration:
Using Javascript
Node 16.16.0, npm 8.11
"snoostorm": "^1.5.2",
"snoowrap": "^1.23.0",
Additional context
That's it, bug only happens when its deployed online and working that way, rather than locally.
The text was updated successfully, but these errors were encountered:
Can't send comment replies - have to wait 10 minutes
So whenever I run my app locally, this rate limit thing never was an issue, I could send comments literally every second, mind you that the bot reddit account is fairly new - around 5 days.
I decided that its ready to deploy on heroku, so I did that, it works every now and then, but the thing is, it gives an error. Only gives it on heroku, not locally.
To Reproduce
Unhandled rejection Error: RATELIMIT,Looks like you've been doing that a lot. Take a break for 9 minutes before trying again.,ratelimit
Expected behavior
I actually am confused why this happens, im not sure if that's because of my config or heroku itself? because as I said, this was not the case when I run my bot locally
System Configuration:
Using Javascript
Node 16.16.0, npm 8.11
"snoostorm": "^1.5.2",
"snoowrap": "^1.23.0",
Additional context
That's it, bug only happens when its deployed online and working that way, rather than locally.
The text was updated successfully, but these errors were encountered: