#leanfucio
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
👋 how may I help?
Hi, I don't get this schedule thing. I know that it has the ability to say when the modification will take effect. You can create a schedule and use a customer to it. my first question is is it possible to use schedule for a specific subscription?
yes
I see that will create a schedule and I can use that object to modify the schedule right?
yes
ok. what about these phases? What if I have a subscription that reoccurs until forever, what should I put in the iterator property? or is it even that property
well the iterations can be as long or as short as you want. Once they "run out" and there are no more phases, if you have end_behavior:release set on the Schedule then the Schedule just ends and the underlying Subscription will just stay in whatever state it was at the end and will recur forever
ok got it.
Sorry for asking a lot. What if a subscription is in the middle of a schedule and then I executed another schedule?
Will it cancel the existing schedule and use the new one? Or will it stack?
you can't have more than one schedule for one subscription
I see.
So, after I create a schedule, it will give an object, then I will use the update method to set up the schedule?
also, how can I say that the schedule phases will start after the billing period?
well it's more that the phases are always happening
when you create the Schedule with from_subscription that creates a new Schedule that already has one phase, which represents the current billing period
to say "change things afer the current period", you call the Update Schedule API passing a phases array that contains that existing phase(you have to re-declare it each time) with e.g. it's end_date:subscription.current_period_end, plus the extra phases you want.
Ok, so basically, to use schedules for my goal is to, create one, and the update it with the all the existing phase that has end_date:subscription.current_period_end so those phases will end after the current billing period. and then I will need to add a new phase (in the same request) to say what will happen next?
along those lines yes. I suggest trying out some code in test mode and also checking the examples at https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#upgrading-subscriptions
Ok. at least I have a more clear view in this schedule thing.
is there a schedules page in the dashboard?
I think so!
Ok. Thanks!