#erin_duplicate-checkout-subscription-and-event

1 messages ยท Page 1 of 1 (latest)

round forumBOT
#

๐Ÿ‘‹ 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.

wanton swan
#

hi there, thanks for your help

rapid marsh
#

Hi! When did this happen?

wanton swan
#

this particular event?

#

(I put the event above)

#

looks like 2025-01-30 04:28:01

rapid marsh
#

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.

wanton swan
#

but then you folks silently removed them w/o sending any webhooks?

rapid marsh
#

Correct. It was a duplicate, so we removed it.

wanton swan
#

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

rapid marsh
#

Ahh ya, that's hard. I'm sorry.

wanton swan
#

why didn't you folks fire the webhooks/events when you removed it?

#

cuz we handle those

rapid marsh
#

(Those being duplicates)

wanton swan
#

they were diff subscription ID's though

#

and no duplicate event ids in our db

rapid marsh
#

Right, but the data should be the same, ya?

wanton swan
#

diff sub id and diff event id

#

how would we tell it's a duplicate?

#

first one

rapid marsh
#

You're 100% right, there's nothing you could have done to reasonably mitigate against this breakage.

wanton swan
#

second one

rapid marsh
#

Can you give me both the Subscription IDs as text?

wanton swan
#

sub_1Qn4LADyl4lnF0w3b5PsUdSY

#

sub_1Qn4LBDyl4lnF0w3Z5JvvnYp

rapid marsh
#

Awesome, ok. I just realized there's not even a way for me to check because the duplicate is gone from my end too.

wanton swan
#

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)

rapid marsh
#

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).

round forumBOT
#

erin_duplicate-checkout-subscription-and-event

wanton swan
#

no worries, shit happens

#

y'all are great

rapid marsh
#

It unfortunately does - and thank you for your understanding.