#saurach - rate limits
1 messages · Page 1 of 1 (latest)
This can happen for any API request if you're exceeding the rate limits we apply.
You will need to make sure you're prepared to detect such errors and handle them gracefully by retrying:
https://stripe.com/docs/rate-limits#handling-limiting-gracefully
Although all my request passes during immediate retry from Stripe, but I dont want these errors in first place . Is there a way to track how many stripe requests are going out from my system at any given point of time ?
Also I am sure that I am not hitting 100 limit (live system ), I think the issue is happening because I am trying to access a busy object .
Yes, these errors specifically about access to an object concurrently
Which can happen in some scenarios
SO yes you may be well under our rate limits, but the concept of handling the 429 errors gracefully with retries is the right approach
It's generally not possible to know if this would happen ahead of time
So you're already doing the right thing by retrying