#taylorcooney_webhooks
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/1397594000168321155
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
So that looks like in one event we removed customer from the payment method and the other we didn't
Not sure offhand why it would happen in 1 vs the other when the detachment is happening for both
Thanks for the quick ping back. Yeah, I wanted to clarify why that would happen in 1 vs the other when the event and workflow to get to the detachment is the same
Yeah I don't know offhand
This is likely an edge case or race condition that the team would need to investigate
Does this happen frequently?
Let me check
We do see this happening, on occasion, more than once. Here is the event ID for another occurance that recently happened: evt_1RguwyKYTiCt9KzSKrZ64Lia
FWIW, these are cards and payment methods that were apart of a migration request and cloned from another Stripe account. e.g copy_from_acct_1KYhlpFP6suHUZ1j_WestDavenportStorage_to_acct_1FkGphKYTiCt9KzS_OpenUnitInc_migreq_1REuNWKYTiCt9KzSRRjvxJWN
All of them? Even the ones where previous_attributes is populated?
Sorry, no. The events where previous_attributes is populated are not part of a migration request
Ok
I wouldn't think that would be related anyway
This is something we'll need time to investigate internally
Can you write in via a link we'll dm you?
Hello @dim moat, we have sent you a direct message, please check it at https://discord.com/channels/@me/1397601667779661966
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
The cards in evt_1Rnm94KYTiCt9KzS3of6fTcs and evt_1RguwyKYTiCt9KzSKrZ64Lia are part of a migration request (clone), and then the card from evt_1RnRlbKYTiCt9KzSUEw9oK67 is not part of a migration request.