#jaunt-products
1 messages · Page 1 of 1 (latest)
hello @uncut blaze! can you share an event id for a customer so that I can take a closer look? it'd look like evt_123
Yes for sure one sec.
evt_1JuA2PDqsmyGk25Qw5NYcxom is a subscription update for a customer which points to a product
prod_KUDn0vkxNFZPMd that was created ad-hoc for a different customer.
The product they purchased originally I believe was created ad hoc earlier than the one it now points to.
alright, give me a while and i'll get back to you, i'm a bit tied up with something else first
ok thank you!
I found a work-around by doing extra lookup into my database based on the stripe customer ID from the webhooks, but of course now I have to go through all my data to see how many times these mysteriously "re-used" adhoc products have been applied to the wrong user.
@uncut blaze sorry, back now, what is the other customer that was using prod_KUDn0vkxNFZPMd?
no problem. one sec
pi_3JeLgcDqsmyGk25Q3IOg4ojU
What's strange for example, is if you look at prod_KZKUrheku9W0we which was created today, the meta data in it is from the user I just sent you who bought several months ago.
Here's another product with the same metadata again. It's old meta data as I can see the version of the software is old (ddcode meta)
prod_KZKU82XL8IlRzG
I take the version of the software and put it in meta data, and so I know it's impossible that I still have that meta data around on my system anymore. So these two products which got created today "adhoc" are using meta data from months ago.
this is going to take a quite a while to look into, sorry about redirecting you but can you reach out to https://support.stripe.com/contact with the details? Once we're done investigating, we'd respond back on the ticket, I don't want to have you wait here while we're debugging. Remember to include two example customer ids where you're seeing this issue should be included