#goliath1879_docs

1 messages ยท Page 1 of 1 (latest)

zenith streamBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1303650182982013011

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

spring hearth
#

๐Ÿ‘‹ happy to help

#

would you mind sharing the request ID where you're getting this error

sturdy sedge
#

unfortunately I couldn't find the request ID. Will it be okay if I share you the customer ID who faced this issue?

#

cus_P1xP1qcfWtjWZC

spring hearth
#

I'll take a look at the account but it's going to take longer without the request ID

sturdy sedge
#

sure

#

I think this is it req_b5FhoSXCT3tc0Q

#

req_zZACeMiI7SSWS3

also check for this

spring hearth
#

taking a look thanks ๐Ÿ™‚

#

I don't see any rate limit on these 2 requests

sturdy sedge
#

can you let me know how did you check if the request hit any rate limit?

#

I can confirm with other requests

#

since this customer complained ... I would have to check for all requests

spring hearth
sturdy sedge
#

req_U9koHMlC15t1YT

spring hearth
#

If you were hitting a rate limit then you would get a 429 HTTP response and you can check that in your logs

#

you don't have any request that is returning a 429

#

which means you're not hitting a rate-limit

sturdy sedge
#

but my customer still got this error

#

can you help me by guiding where to look into?

#

this is not rate limit but object lock timeout I believe

spring hearth
#

this is not a rate limit

#

what are the API calls that you're calling?

sturdy sedge
#

only stripe.CreateSetupIntent while adding address details or card

#

apart from this stripe.CreatePaymentIntent

spring hearth
sturdy sedge
#

yess

spring hearth
#

I don't see any 429 requests in your logs

#

it's really bizzare

#

unless you're using another account or a connected account

#

when did that happen?

sturdy sedge
#

yesterday

spring hearth
#

taking a look

zenith streamBOT
agile harness
#

this can happen sometimes especially when using a Stripe account in India, because of some of complexities with local data locality. If you feel it's happening too much I'd suggest opening a support ticket/raising with your sales contacts. At a technical level I can't suggest anything else but retry the request until it succeeds.

sturdy sedge
#

retry needs to be triggered manually by the customer

#

which is not efficient way and also annoying for the customer

agile harness
#

yep I agree it's problematic

sturdy sedge
#

can you guide me how to use the stripe.max_network_retries in such cases?

sturdy sedge
#

the documentation for this property is lacking on stripe website

agile harness
#

what information is not there that you're looking for specifically?

sturdy sedge
agile harness
#

globally EDIT : or rather, global to the everywhere you use the same StripeClient instance

sturdy sedge
#

also can you confirm if I can check for 429 response code when any customer faces the object lock timeout issue

agile harness
sturdy sedge
#

okay thanks for all the help