#celohealth_unexpected
trim depotBOT
đ 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/1361491922677665902
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
nova moss
hello! I believe the default payment method is set on the subscription
do you have a subscription id which i can look at?
dry marsh
sub_1RDwkBDx7BwidrH0gReYmBBm
nova moss
yep, the default payment method is set on the subscription itself. You should be able to view that if you retrieve the subscription or listen for the subscription related events
dry marsh
I have a subscription and scheduled a change of product type on the subscription for a following phase. I fast forwarded the test clock to after the phase was scheduled for. The change was successfully applied but for some reason another schedule was added to the subscription going from the previous product type to the new product type.
This is the subscription sub_1RDzCvDx7BwidrH07MeGXYoz. You can see that it is a Business subscription but there is a subscription schedule for Business Pro -> Business which it is already in.
nova moss
gimme a while, will take a look in a bit
nova moss
I'm assuming this is the request where you scheduled the change? https://dashboard.stripe.com/test/logs/req_zho9YlsEYbRra7
I'm probably missing something obvious, but where are you seeing in the subscription schedule, where you mentioned another schedule was added to the subscription going from the previous product type to the new product type.
dry marsh
On this subscription https://dashboard.stripe.com/test/subscriptions/sub_1RDzCvDx7BwidrH07MeGXYoz
When the test clock was frozen on 29 April 2025 the schedule was set for Business Pro -> Business with Bills on 29 April 2026 for 1 Year
After fast forwarding i expect there to be no more phase/schedule but as shown in the screenshot it is Bills on 29 April 2027 for 1 Year
nova moss
your phase 0, ends at 2026-04-29 02:25:14 UTC. Subsequently, there is a phase 1 which will end 2027-04-29 02:25:14 UTC
everything looks fine (as expected) to me
that's the same as the response in this request : https://dashboard.stripe.com/test/logs/req_zho9YlsEYbRra7
dry marsh
Am I missing something?
from the request i made phase 0 is between 2025 - 2026 for the Business Pro Price
nova moss
yeah, but you also have a phase 1 which is one iteration long
dry marsh
phase 1 is for the Business price.
what does having one iteration do to the phase?
what documnetation can i refer upon
Is the phase created for the current product NOW and then runs 1 iteration
or is the phase created for the product on the subscription when the phase is expected to execute?
nova moss
https://docs.stripe.com/billing/subscriptions/subscription-schedules#phase-length - this explains what is a phase and and iteration. If you have a yearly price, one iteration means 1 year
I don't quite understand last two questions though, maybe can you rephrase after going through that section of the guide I shared?