#goliath1879_docs
1 messages ยท Page 1 of 1 (latest)
๐ 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.
- goliath1879_unexpected, 4 days ago, 44 messages
๐ happy to help
would you mind sharing the request ID where you're getting this error
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
I'll take a look at the account but it's going to take longer without the request ID
would you mind searching for it please
https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
sure
I think this is it req_b5FhoSXCT3tc0Q
req_zZACeMiI7SSWS3
also check for this
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
would you mind sending me those request IDs?
req_U9koHMlC15t1YT
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
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
only stripe.CreateSetupIntent while adding address details or card
apart from this stripe.CreatePaymentIntent
is this in live mode?
yess
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?
yesterday
https://dashboard.stripe.com/logs?object=cus_P1xP1qcfWtjWZC
this customer faced the same issue (object lock timeout)
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
taking a look
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.
retry needs to be triggered manually by the customer
which is not efficient way and also annoying for the customer
yep I agree it's problematic
can you guide me how to use the stripe.max_network_retries in such cases?
the documentation for this property is lacking on stripe website
what information is not there that you're looking for specifically?
in any case, I don't think we automatically retry on a 429 lock timeout(see the code at https://github.com/stripe/stripe-python/blob/master/stripe/_http_client.py#L182-L227) so that parameter probably doesn't help. You can try/catch each API call and manually retry overall.
So I was confused where to set the max_network_retries while creating setupIntent or paymentIntent or it should be set globally
globally EDIT : or rather, global to the everywhere you use the same StripeClient instance
overall read https://github.com/stripe/stripe-python?tab=readme-ov-file#per-request-configuration which explains how you can create and use StripeClient with additional options like this one
also can you confirm if I can check for 429 response code when any customer faces the object lock timeout issue
yes you can wrap calls in try/catch blocks to catch errors they raise https://docs.stripe.com/api/errors/handling?lang=python
okay thanks for all the help