#kamran5446

1 messages · Page 1 of 1 (latest)

supple bobcatBOT
drowsy wave
vestal mica
#

why stripe is giving this exception of "This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate."

drowsy wave
vestal mica
#

what are the drawback of this exception?

#

stripe.max_network_retries = 2
i am unable to find a way to limit this network request in djstripe.
retries are performed by stripe.

drowsy wave
#

i am unable to find a way to limit this network request in djstripe
What do you mean by that?

#

If this is part of the integration controlled by djstripe, you may need to reach out to the developer for help with that, to understand if your use case is supported

vestal mica
#

to solve this issue. i need to limit the max_network_retries ? right?

drowsy wave
#

Not neccesarily, a lock timeout means something else is accessing the object, which might be an entirely different request

#

Can you share the exact request ID where you hit the error so I can look?

vestal mica
#

req_red55E8FlXf3Nz

drowsy wave
#

When do you make this get request in your code? Are you creating or updating anything just before that?

vestal mica
#

its occurs during different webhook execution, lets say invoice creation or invoice deletion

drowsy wave
#

Ah, it looks like you might be calling that right after say invoice.finalized or paid

#

And the customer is still locked related to some of that processing

#

if you get that error, you should be able to add a small delay and try again

vestal mica
#

basically, stripe is already retrying it multiple times? why shoud i need to increase one more time retry?

supple bobcatBOT
drowsy wave
#

We aren't retrying it -- that's something a given integration decides to do or not

vestal mica
#

alright