#sean-lanning_webhooks
alpine elmBOT
👋 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/1310618726583894037
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dapper vortexBOT
barren galleon
Hi there 👋 I also see two delivery attempts for that Event to a single webhook endpoint, at the same time, even though both were successfully delivered. This seems unexpected, and I'm looking to see if I can spot why it happened.
charred dew
Yea we successfully received both events, but it caused a duplicate transaction in our accounting system since the events came simultaniously
barren galleon
I'm not spotting any discussions of this so far on my side, but am still looking.
charred dew
OK
I was going to reach out to Support, but I thoought the Dev channel might have more insight
barren galleon
Unfortunately I'm not spotting any mentions of this so far, so I don't have insight into what could have caused it. Getting that insight will take a deeper investigation than I can provide here, and I do suggest reaching out to our Support team to start that if that insight is crucial.
https://support.stripe.com/?contact=true