#stripe_connect_platform-PricingUpdate
pastel iron
the object id?
which object?
That is the thing. I am looking in the dashboard and i watched as the count increased on 1 and decreased on the other right? but now the count of the collection is greater than it should be. I don't know which object is the object in the collection of objects but I know that the count on the collection of objects is higher than it was prior to the pricing update
The only API calls we made were:
stripe_sub = Stripe::Subscription.retrieve(id)
and
Stripe::Subscription.update(stripe_subscription_id, plan: ENV['price'], proration_behavior: 'none')
that's it
warped herald
Sorry, I should have been clearer.
pastel iron
Can you look at my account and see in the last hour if anything really bizarre happened?
Did I re-instate canceled people somehow or add a 2nd sub somehow?????
warped herald
It would look like price_xxx
pastel iron
oh sure
I did (A) monthly and (B) annual price increase
The old monthly price ID was:
5
yes, 5
The new price_id is price_1LLYFbHnzkM7EAuHHIVHPDAD
The old annual price was 6
yes, 6
The new annual price_id is:
price_1LLYGbHnzkM7EAuHfph6f0Gf
It says I have 79 people on price_1LLYGbHnzkM7EAuHfph6f0Gf
But, I did not have 79 people on 6.
?????
1 person didn't migrate over....i think because he canceled so there is 1 person left over on 6 and everyone else (along with some mystery people) are now on the new price.
?
No one was charged today. So i don't see how I could have taken someone on an inactive sub and put them on a new sub??? Hmmmmm.
I am so happy that no one was charged now for whatever is happening. But....I would love to solve the mystery and clean it up before anyone is charged. 🙂 !!!!!!!!
brb
I ran this code in the last 2 hours.
Do you see that I have an increased count of Customers? or an increased count of Subscriptions? in the last 2 hours? Just guessing here.
warped herald
Looking into this on my end, trying to figure out what happened.
When you state you migrated to a new price, what action did you specifically take?
These two prices are for two different product ids, prod_BTnwLIDTYeD2FW and prod_BpijfJV0jXXsIM
What were you ultimately trying to achieve?
warped herald
koopajah is not here but I'm trying to better understand what you were trying to do so I can further assist.
fair chasm
Hello! I'm taking over and catching up...
pastel iron
'back-in-the-old-days' one could just update a price. Everyone on that price id was grandfathered in, but maybe you didn't show them as active on that price_id since technically they were paying a lower price. That's honestly why we did the price update .....to get things cleaned up and everyone on the same price_id paying the same amount.
fair chasm
Looking at your logs you updated many different Subscriptions to that new Price. Have a look here in the Dashboard at your request logs: https://dashboard.stripe.com/logs
pastel iron
yes many
everyone
everyone on that plan was moved to the new price
but everyone on the old price was X and not eveyone on the new price should be X b/c it is all the people
but X > X
The count of subscribers increased!
That's my mystery
fair chasm
X isn't really helpful, honestly. You mentioned before:
Now the old price subscriber count is 0 but the new subscribe count is X times so number greater than 1.
Does that mean X is a multiple of the original subscriber count, or just more?
pastel iron
I don't remember the original. It was something like 41 and now is 75 ish
fair chasm
Like are you saying the original subscriber count was 5, and now it was multiplied by 3 to 15? Or are you saying the old one was 5 and it's now increased to 7?
Okay, so it didn't double, but it did increase quite a bit.
To clarify, you're sure all of these Subscriptions were on the same plan before the update?
fair chasm
Let me look at some of them, hang on...
pastel iron
so looking at the total, it is pretty close to our db totals so it looks about right now give or take a margin of error.
Before the update, I think those totals were vastly understated like by about 50%.
I think it was understating due to the way we used to increase price. I know koopajah did not like that we were doing it that way and recommended not doing it that like. This is one of the reasons we did the update to take his excellent advice.
fair chasm
Yeah, so not all of these Subscriptions were on the same plan before this update. That's likely the reason for the counts being not what you expected.
fair chasm
I'd rather not give you a Subscription ID as I can't verify your identity here, but I'm happy to give you this request ID which you can load in your Dashboard to get the Subscription ID: https://dashboard.stripe.com/logs/req_z2sj8XzkccQ9Rf
pastel iron
ok sure hold on
fair chasm
Note the most recent Event on that Subscription.
pastel iron
that one is confusing since he happened to be on a billing cycle that billed today but...
that one looks good to me
We had a plan that was $29.97 and now is $39.97.
fair chasm
Maybe I'm confused. What plan were you expecting this to be on prior to the update?
5 or 6?
pastel iron
one sec
6 => price_1LLYGbHnzkM7EAuHfph6f0Gf
6 is now that
that is/was our annual pricing on that plan
5 => price_1LLYFbHnzkM7EAuHHIVHPDAD
5 is now that
Sorry I see that his billing cycle was on the 3rd. He was billed today at 1:47pm at the old price. I ran the update after that. So he will be billed on Sep 3rd at the new price. 🙂 That one I'm good with. That was the goal.
fair chasm
Okay, so just to make sure I understand, all of the Subscriptions on 6 should have been updated to price_1LLYGbHnzkM7EAuHfph6f0Gf and all of the Subscriptions on 5 should have been updated to price_1LLYFbHnzkM7EAuHHIVHPDAD?
pastel iron
!!! totes. yes.
i think you understate it when people are on an old price with the same id
which is not allowed anymore but used to be the way we did price updates
fair chasm
Yeah, I'm seeing here that you had multiple plans with an ID of 5 over time.
pastel iron
right!
that's what we are/were fixing up! 🙂
how do you see that? Is that something I can see? Or can you get the count of all the people on ID 5?
Now its 0 or 1 maybe but about 2 hours ago it much higher but not matching the count now
fair chasm
So that Subscription we were just looking at, that one was on an old deleted version of 5, and it was updated to price_1LLYFbHnzkM7EAuHHIVHPDAD, but I'm also seeing other Subscriptions which were on a different 5 that isn't deleted that were also updated to price_1LLYFbHnzkM7EAuHHIVHPDAD. That's expected?
pastel iron
Any version of 5 was the same plan
And they are all moving to the new price_xxxxxx
So yes, expected
i built the app in 2016 and used [1,2,3,4,5,6] as the plan ids. 🙂
over time i increased the price of each by just updating the "Plan" with that ID.
I think the updating to the new price_xxxx increased the count in the dashboard to the actual total subscribers. And that the dashboard undercounts (ignores) people who were on "an old deleted version" of a given price_xxxxx
That is my hypothesis at this point.
If that is the case, I'm happy and all is good.
But I am open to anything you are seeing. Best to get it fixed now before anyone is charged.
fair chasm
I believe you're correct. Inside Stripe a deleted plan with an ID of 5 is a distinct and separate object from a different plan with an ID of 5 (those two plans have two different IDs internally).
So the Dashboard would only show counts for one of them.
pastel iron
but that dashboard rolls them all up but seems to ignore related objects of an old pricing amount
right!
OK i am super happy
fair chasm
In your screenshot you would only see the counts for the ones that aren't deleted.
pastel iron
We totally messed up the last price increase much worse. 🙂
OK great.
Thank you so much. Today was hard and having you guys look at things really helped!!!!!!!
fair chasm
Glad we could be of service!
fair chasm
Nope, but if you have any other concerns please let us know!