MidnightCrow | Stripe Developers | Page 1

novel bisonBOT May 4, 2023, 2:06 PM

#

clear ether May 4, 2023, 2:06 PM

#

Hi there

#

Sure, can you share the request ID?

#

Is it a lock error?

#

Or a rate limit?

tiny ravine May 4, 2023, 2:06 PM

#

req_7ry5xvVad0siwy

#

what is the difference

clear ether May 4, 2023, 2:08 PM

#

Well one has to do with the number of requests you are making at the same time and the other has to do with attempting to access the same object while another request is handling that object. Have you read through https://stripe.com/docs/rate-limits#object-lock-timeouts yet?

tiny ravine May 4, 2023, 2:09 PM

#

hmm yes it seems like the lock error, thats what I am asking. If you could tell me which two calls are causing the issue

clear ether May 4, 2023, 2:11 PM

#

Looks like it is being help due to actions involving an Invoice for that customer at the same time

#

Looks like specifically finalizing/paying in_1N3huoDKXn4ivDe3PWCi9SLq which was happening concurrently

tiny ravine May 4, 2023, 2:14 PM

#

both of those calls have a status 200, and they are one second after each other. This wouldn't match up with when I am seeing the error either.

clear ether May 4, 2023, 2:15 PM

#

That's not how it works

#

Finalizing an Invoice and then the subsequent payment of it may take several seconds, even if the response from the API request itself is a 200 immediately.

#

There are various processes that go on behind the scenes, especially with Invoices

#

During that time, you can't access any object related to that Invoice, like the Customer

#

If you hit these errors you basically need to space your requests out a bit more and have a retry policy in place

#MidnightCrow