#michael_unexpected
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252180058416611338
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
Hi, let me help you with this.
What are you trying to achieve exactly, on the high level?
Start date is when the Subscription actually starts, the first phase of the Subscription Schedule comes into effect, and the customer is billed for the first time (if applicable).
When is the subscription going to have the state of "released"
thank you for your fast response btw
A Subscription Schedule is released after it reaches the end of the last phase, given end_behavior=release: https://docs.stripe.com/api/subscription_schedules/object#subscription_schedule_object-end_behavior
Or, if you manually release the Schedule: https://docs.stripe.com/api/subscription_schedules/release
After that, it becomes just a normal Subscription, keeping its latest configuration.
“The subscription is managed by the subscription schedule xxx, and updating any cancellation behavior directly is not allowed. Please update the schedule instead.”
so how could we cancel/release the subscription according to this error?
You send a request with the Subscription Schedule ID to the relevant SubSchedule endpoint, not to a Subscription one.