#yagnesh_error

1 messages ¡ Page 1 of 1 (latest)

sour scaffoldBOT
#

👋 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/1468863817499934901

📝 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.

heady thunder
#

Hey @patent slate Could you send me the request where you received this error?

patent slate
# 
  "error": {
    "code": "lock_timeout",
    "doc_url": "https://stripe.com/docs/error-codes/lock-timeout",
    "message": "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.",
    "request_log_url": "https://dashboard.stripe.com/acct_163V6mH1e3zUAJEx/workbench/logs?object=req_sEvWCUlZt7LGLL",
    "type": "invalid_request_error"
  }
}```
#

this is full object i found

heady thunder
#

Yup, so like what I mentioned above, there was another API request that was accessing the Payment Intent: pi_1SxMC4EDAKzxgDEHObKGuMe1 at that time.

Looking at the timeline:

  • 2026-02-05 06:37:47 UTC: A Payment Intent Confirmation call was made, triggering 3DS authentication
  • 2026-02-05 06:38:05 UTC: 3DS was complete
  • 2026-02-05 06:38:07 UTC: The GET call (req_sEvWCUlZt7LGLL, the request you sent) was made
#

So the GET call was made when the Payment Intent was still getting updated.

#

If you try the GET request now, you would most likely not see the error

#

I would suggest that you either space your requests out or rely on events such as the payment_intent.succeeded event to trigger the next request

patent slate
#

Okay thanks for the clarification.
Also is it possible that I can get this error for checkout session too? if yes then does this affect the receving the webhook events

heady thunder
#

Also is it possible that I can get this error for checkout session too? if yes then does this affect the receving the webhook events
It depends on how your checkout session integration flow is designed.

#

If you are immediately calling a GET request after the Checkout Session is completed or Payment Intent is Confirmed, then this error might be more common:

What you can do to prevent them:

  • Make less GET requests, for example by storing the results to variables after the method calls, reducing the need for a GET call
  • Avoid making API requests in parallel, instead do them sequentially and spaced out
  • Implement webhooks which listen to events before firing the next request e.g. after receiving the checkout.session.completed event, you can then call GET checkout sessions,
sour scaffoldBOT
patent slate
#

Okay thanks for the information, this error does not stop my payments to complete right?

heady thunder
#

Generally GET requests wont stop your payments from completing, because they are not like POST requests (e.g. Payment Intent Confirmation), which try to update the object