#HappyCathode
1 messages · Page 1 of 1 (latest)
No it's actually InvalidRequestError. RateLimit is a different thing when you can't have more than 100 request per second
can't "you're creating accounts too quickly" be rephrase "the rate at which you're creating account is too high" ?
I have some retry mechanism in place for when a stripe.error.RateLimitError error pops up, but I feel like I should should not do a retry on a "stripe.error.InvalidRequestError". My request is not wrong, malformed, or invalid
shouldn't a request be considered invalid if it's own parameters are invalid, instead of the amount of other requests that were sent ?
That's actually sound fair. qq What status code and what is the detail error you got there?