#donna_webhooks
white prawnBOT
👋 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/1363971695899181226
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sick spire
Hello there
late jackal
Hi!
sick spire
It is very possible for there to be duplicate Events created, see: https://docs.stripe.com/webhooks#handle-duplicate-events
You have to handle this gracefully on your end.
late jackal
While I'm reading it, why does this happen?
sick spire
I don't recall the technical reason exactly. It has to do with our internal infrastructure/partners who help facilitate these Webhooks.
late jackal
Do you have an in-depth article? It only shows little on how I could get it done. 🙂
sick spire
An in depth article for how you would handle knowing the Events are duplicates?
late jackal
How to prevent duplicate evenets
sick spire
No there isn't a more comprehensive article. This is slightly more complicated for invoice.upcoming since the Event won't actually contain an Invoice object ID. But you can check the data... for instance you could look at the Subscription ID. Or you could track on your end if you already handled the Event -- that mostly depends on what you are using the Event for exactly and your own internal systems.
late jackal
How can I prevent it?
Doing the manual to track the already handled events negates the use of webhook and automations
sick spire
You can't prevent it.
I already explained that -- you have to handle this on your side.
late jackal
When the webhook is triggered, it sends a message to Slack.
sick spire
Then you'll need logic to check if you already performed that action for the relevant Subscription