#antoineb_api
vocal oliveBOT
👋 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/1416065836027744409
📝 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.
- antoineb_docs, 2 days ago, 26 messages
slow ice
Hi, taking a look at the request id
spark sierra
here's another request req_6MEkR1XTmbLaEC that re-uses the same response because of idempotency
slow ice
This is expected if you're reusing the original idempotency key, you'd continue to see lock_timeout errors as idempotency keys are cached for ~24 hours and we just return the original response: https://docs.stripe.com/rate-limits#object-lock-timeouts
This is not really a good use case for idempotency/retries. They’re only intended for when the outcome of the request is unknown (i.e. a 5xx response)
You would either need to wait 24 hours or make that request with a differen idempotency key
spark sierra
okay, thanks!