#cpapazach_unexpected
lapis caveBOT
👋 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/1232609655231090689
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
finite patioBOT
stuck hawk
hi! do you have a subscription ID sub_xxx where that happened?
warm veldt
yes let me get it for you
I have 2 cases
First one : sub_1Mpto9FE3Qfj39xWjbdMV3PL
(So you see that on the anniversary of 1yr this one got updated)
Second one : sub_1MvxF3FE3Qfj39xWJRSCLVGa
stuck hawk
it's because you used a SubscriptionSchedule to create that Subscription, and when you direclty update the Subscription object to change the current price, that only changes the current phase, future phases would still use the old price; when doing updates to a Subscription manged by a Schedule you also need to update all the future phases of that Schedule so they incorproate the change.
warm veldt
Oh I see thanks a lot makes sense tbh.
How do I update all future phases as well? Is there some relevant configuration/field ?
stuck hawk
https://docs.stripe.com/api/subscription_schedules/update but it's a bit complicated since you have to pass every phase, each time(you can't pass just the parts that have changed), you would need to get comfortable with this in test mode
https://docs.stripe.com/billing/subscriptions/subscription-schedules#updating
warm veldt
Thanks a lot
Will dive into the docs and try to fix in the test mode first with test clocks
I think I have all I need
thanks again for your prompt response 🙏
stuck hawk
no worres, unfortunately this is a know pain point and failure mode
i.e you have a schedule that says
date x -> date y Price A
date y -> date z : Price A
date z -> forever : Price A
if it's currently some time between x and y, and you call the Update Subscription API and change the subscription to Price B, that only changes the current state, the 2 next phases still stick to Price A so the Subscription flips back to it on date y.
AFAICT that's what is happening in your example