It seems the API 429 error is back again. This is kind of frustrating, to be honest, if you're paying for it.
#429 error. Too many requests
vocal crow
midnight notch
It seems the API 429 error is back again. This is kind of frustrating, to be hon...
same thing with me
vernal cape
vocal crow
though I'm handling this so that my app won't crash, it still prevents my app to scale
sick orchid
did you guys fix his issues?
I'm still having this issue... I wish the official account gave us some announcement for this.
oh, it's fixed. sorry!
velvet crag
I am still getting this with pretty much every request, and I am just calling it manually locally, one at a time, every minute or so.
edgy jetty
Are you on a pay-as-you-go account?
vocal crow
Are you on a pay-as-you-go account?
yep.
Not getting this error today but will keep on monitoring the performace of the API
edgy jetty
Got it, there was an incident earlier so that may have affected things
vocal crow
Most probably. Thanks for the help.
edgy jetty
No prob
flint pelican
I'm not sure this is the right place, I see lots of 429 threads. Anyway...
For anyone facing the 429 error with type insufficient_quota, we solved it by specifying the Hard limit. Our configuration only specified the Soft limit, but it seems insufficient.
The missing max limit in the "Usage this month" progress bar on the "Usage" page was a hint of the problem.
I would consider this a bug because
- The Hard limit is not required.
- The Approved usage limit should work as the default hard limit.
I suspect a bug in the way the max limit is set.
I hope this could help someone else