#chris-vr_webhooks
native glacierBOT
đ 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/1285597149488353332
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
supple loom
We don't have public details on those retry schedules, but in live mode the first retry is generally fairly soon.
For example with event you shared, the first retry happened after 15 seconds
lusty nexus
exactly I see the first happen in less than a minute
exactly so if in those 15 seconds I am unable to handle still then I need to wait for the third which I am not sure how long takes
supple loom
Yep, then 2nd and third retries could be quite a bit longer, so you'll want to ensure your endpoint is available and able to respond, especially if you have a sensitivity to event delivery
lusty nexus
when you say a bit longer can it be more than 15mins?
I currently wait 15 mins before processing the order
which I can increse to be safe if necessary
supple loom
Yes, some redeliveries will be longer than 15 minutes
In live mode, Stripe attempts to deliver a given event to your webhook endpoint for up to 3 days with an exponential back off. In the Events section of the Dashboard, you can view when the next retry will occur.
lusty nexus
awesome, thanks!