#ali-raza-khan_webhooks
subtle harnessBOT
👋 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/1305872819866828810
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
copper mesa
yes I agree, I can see that the URL is accessible
timeout could be a result of a long operation on the webhook endpoint that is taking more time than the allowed TTL
prime prairie
we just send a 200 to the webhook and than process if anything needs processing
copper mesa
we recommend using a fire-and-forget approach when it comes to responding to Stripe's event requests
prime prairie
i just confirmed from the codebase that whenever a webhook lands on our server, we just queue it and send a 200
can you let me know what is the accepted response time from Stripe. Meaning for how much time Stripe waits before marking the webhook as timed out
copper mesa
could the queue be full at some point which makes it impossible for the queuing to happen fast?
prime prairie
No
copper mesa
would you mind checking https://support.stripe.com/questions/webhooks-how-to-investigate-and-fix-timed-out (especially last point) ?
copper mesa
I really can't help since I don't have access to and visibility of your infrastructure
prime prairie
can i somehow set the timeout for the webhooks request?
copper mesa
no unfortunately you can't change that since we're sending the request to your server and not the other way around