#nick - rate limit

1 messages · Page 1 of 1 (latest)

cedar sphinx
#

You can contact support describing your use case here and why you need a higher limit, butI don't know if it will be possible to accommodate.

#

Generally my advice would be to keep the test mdoe requests limited, possibly by disabling some functionality if needed, where it doesnt affect the thing you're trying to test

final sedge
#

Yeah we've only really hit the limit today, we have a pretty true-to-production test environment that the whole company uses for testing/etc. I plan to implement some caching on our end to limit calls to Stripe but that'll take some time so hopefully support can increase the limit for a couple weeks

cedar sphinx
#

Is it bursts of batched requests doing it?

#

If you're sharing a single account with many developers/environments the easiest approach might be to just set each dev up with their own account

final sedge
#

That's something we thought of, but I'm kind of the sole Stripe "Administrator" in the company so most people have no idea that Stripe is even there in the backend.

Yeah it'll be like bursts of unit tests, testing adding a credit card and creating a subscription through our UI/backend->Stripe

#

integration/end2end tests essentially. A suite as close to prod as you can get

cedar sphinx
#

Right, so either throttling those or partitioning across accounts are likely to be better options than a higher limit, which would eventual succumb to the same issue as your test suite expanded.