#erin_duplicate-checkout-subscription-and-event
1 messages ยท Page 1 of 1 (latest)
๐ 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/1336456665486200984
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there, thanks for your help
Hi! When did this happen?
I think that confirms it then - thanks. ๐
Between 18:23โ22:09 UTC on 2025-01-30, some users experienced an issue wherein Checkout integrations emitted two customer.subscription.created events for each completed Checkout Session.
The issue has been resolved. The duplicates can safely be ignored.
Iโm sorry for the trouble this has caused. Please let me know if you have any additional questions.
but then you folks silently removed them w/o sending any webhooks?
Correct. It was a duplicate, so we removed it.
in the future, how would I code against that?
we have an Orphan sponsorship feature where folks can sponsor an orphan and this triggered another orphan sponsorship
so this is a pretty big deal that this happened
Ahh ya, that's hard. I'm sorry.
why didn't you folks fire the webhooks/events when you removed it?
cuz we handle those
You handle subscription cancellations, but in this case, no actual Subscription object was created - it was a duplicate event of an already existing Subscription.
We talk about how to handle those here: https://docs.stripe.com/webhooks#handle-duplicate-events
(Those being duplicates)
Right, but the data should be the same, ya?
You're 100% right, there's nothing you could have done to reasonably mitigate against this breakage.
second one
Can you give me both the Subscription IDs as text?
Awesome, ok. I just realized there's not even a way for me to check because the duplicate is gone from my end too.
hokey dokey, if there's nothing we could have done and nothing we can do, guess that's all for now (I'll be back cuz we have a few other quirks for me to research)
The overall on this is that this was a Stripe breakage - which does occasionally happen, though we obviously try to do it as little as possible - and there's not really any way y'all could've known this short of
... asking here, or any email outreach we did (which I thought we did).
erin_duplicate-checkout-subscription-and-event
It unfortunately does - and thank you for your understanding.