#vienklett_webhooks
modern condorBOT
đ 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/1377028808934166598
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
dense cloud
So sorry. Reading now.'
raw void
no worry. thanks
dense cloud
Where did you get that error?
raw void
i went to my webhook, check on checkout.session.completed event, and saw it failed
dense cloud
What is the Event ID?
dense cloud
That's the response from the server at the webhook endpoint - i.e., that error message is coming from y'all.
https://docs.stripe.com/rate-limits#object-lock-timeouts
Most likely y'all made some request inside your webhook handler code for which we returned a 429 lock_timeout, but which y'all didn't then retry - likely because you didn't have code to handle that error and so it was then surfaced as a "server error" in your response to Stripe.
raw void
Thanks. i will look into it.