#meags-teamvash_best-practices
glacial otterBOT
đ 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/1222244368979591249
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hollow mulchBOT
solar rain
Hello! No, we don't have a built-in way to test that, but you can send the same Event payload to your own Webhook Endpoint URL again.
outer spruce
Hello! No, we don't have a built-in way to test that, but you can send the same...
Ah that makes sense, thanks!
@solar rain If an event was sent twice, would the timestamp be the same? Trying to determine to use the entire event payload as the idempotency key or just part of it
solar rain
I recommend you use the Event ID as the idempotency key.
The Event object itself should be identical, but other parts of the request may be different.
outer spruce
I recommend you use the Event ID as the idempotency key.
Ah perfect, the event id stays the same, I'll use that then, thanks!
solar rain
For example, let's say we try to deliver Event A to your endpoint and our request to your server succeeds (meaning you got the Event) but your response to our server fails (meaning we don't know you got the Event). We're going to retry sending that Event, so you'll get a second Event A request from us with the same Event inside, but the headers/signature/time will be different because it's a separate retry request.
outer spruce
For example, let's say we try to deliver Event A to your endpoint and our reques...
Makes perfect sense, that explanation about how the response to the stripe server could fail like that helps me wrap my head around it, cheers!
solar rain
Happy to help!
solar rain
@outer spruce We don't normally reopen threads, but a colleague pointed out that I completely forgot about Stripe CLI's resend command, which allows you to resend Events: https://docs.stripe.com/cli/events/resend
That makes sending the same Event to your Webhook Endpoint twice easier than manually sending the payload again yourself.