#martin-gaibisso_webhooks
languid sparrowBOT
👋 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/1428776932824318023
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
uncut pumice
why the same second?
slate mountain
👋 Hi Martin, taking a look at the Event id.
It looks like we sent the event once and your server responded twice with both a 200 and 400.
slate mountain
sorry, juggling a few threads, looking a little closer.
slate mountain
appreciate the patience (and yeah you are right about that, need more coffee this morning) have you seen any other examples of this happening?
slate mountain
I think this might be a one off, from looking over the logs. We have some guidance on how to handle these occasional occurences.
https://docs.stripe.com/webhooks#handle-duplicate-events
languid sparrowBOT
uncut pumice
no, getting a lot of these since 2 days ago
started happening out of the blue
only with transfer.created events
slate mountain
if you can share a few more of those examples, maybe we missed them. It would still be advisable however to follow those docs to make sure things work smoothly when it happens.
proven goblet
Sending the duplicated event is expected. I'd recommend checking this this doc https://docs.stripe.com/webhooks#handle-duplicate-events on how to handle duplicated events:
Webhook endpoints might occasionally receive the same event more than once. You can guard against duplicated event receipts by logging the event IDs you’ve processed, and then not processing already-logged events.
In some cases, two separate Event objects are generated and sent. To identify these duplicates, use the ID of the object in data.object along with the event.type.
uncut pumice
ok, ty