volco

[muted zinc]

Hello! For your first question, if the Subscription Schedule's end_behavior is set to cancel it will cancel the associated Subscriptoin at the end and then the Subscription Schedule's status will be completed.

For your second question, I'm not sure I fully understand, but you can release a Subscription from a Subscription Schedule at any time using this API: https://stripe.com/docs/api/subscription_schedules/release

[ivory panther]

Thanks! Yeah I thought about manually releasing it but was wondering if there was a default way of releasing it. I wondered if this was possible because when you try to cancel the subscription that is created during the Subscription Schedule's active phase, you get an error saying that you can't cancel using the Subscription API because the subscription is still being managed by the SubscriptionSchedule and you have have to update the schedule instead. To me this was confusing as logically once the Subscription is created, you should be allowed to manage it directly instead of having to indirectly update the Schedule which then updates the Subscription for a whole billing cycle. I guessed that was the effect of having the Schedule in status 'active' for the duration of the phase

[muted zinc]

Not sure what you mean by a "default way of releasing it"?

Is the core quesiton "how should I cancel a Subscription which is being managed by a Subscription Schedule?" or is it something else?

[ivory panther]

I think you've answered my question. It seems my best bet is to just release a schedule right away after it becomes 'active'. Is there any downside/considerations for never letting a phase run its full course (immediately ending it after it starts)?

Or in the other words, what's the benefit of having a phase if the array of phases is only 1 phase?

[muted zinc]

Ah, I see. So you're really only using Subscription Schedules to start Subscriptions in the future?

If that's the case you can release them after they start the Subscription, sure.