Eranga-error | Stripe Developers | Page 1

edgy wedge Oct 21, 2021, 10:12 AM

#

@glossy ingot there's documentation on this at https://stripe.com/docs/rate-limits#object-lock-timeouts
As for the object that was actually locked, if you have the req_xxx I might be able to find out, I've looked at this before

glossy ingot Oct 21, 2021, 10:14 AM

#

Let me check whether I can find the request ID

#

Is it logged in somewhere in Stripe? Because I cleared my logs 😦

#

Is it this req_iENoPfVHToKQP7

edgy wedge Oct 21, 2021, 10:18 AM

#

thanks; yeah it's in your screenshot, on the dashboard logs page

#

in this case it's a lock on the Customer object

#

checking maybe what else was happening at the time

glossy ingot Oct 21, 2021, 10:22 AM

#

Thank you, let me know if you find more information. In the meantime I had a glance through the document you sent. It seems like we can set a retry for 429 errors.

#

I added it like this

#

It was 2 in the documentation. Do you have a recomended value for this other than 2? 🙂

edgy wedge Oct 21, 2021, 10:25 AM

#

it's up to your tolerance , with higher values the overall time it takes an API request to complete (like the function to return a value) can be longer, which might mean your UI spins for longer. Probably best to start with the default

#

so yeah you were confirming a PaymentIntent that was for the same customer at about the same time (As you said you're paying unpaid intents for them) so a lock error on the customer is not terribly unusual, best option is to retry yes.

glossy ingot Oct 21, 2021, 10:28 AM

#

Very nice. I didn't think about Stripe's end when trying to send the API requests. So I send multiple intent requests at the same time. So like you said we should be careful not to do that.

#

That is all for now. Thank you for your time on this.

#Eranga-error