#john-l_subscription-schedules
1 messages ¡ Page 1 of 1 (latest)
đ 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/1388180708715135028
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi, I see you're still typing here. I will wait ..
Maybe this is more of a code question, but I've seen a few ways to handle this. One option is to change our process to rely more heavily on subscription schedules so we manage subscription schedules when a user downgrades rather than tracking these ourselves. Another option is to release a subscription schedule if it's in the final phase and continue our self-managed process of downgrading or upgrading
thanks !
Hi, yes we have this guidace: https://docs.stripe.com/billing/subscriptions/subscription-schedules you can review. Specifically, here: https://docs.stripe.com/billing/subscriptions/subscription-schedules#downgrading-subscriptions
Let me know what specific questions you have after reviewing these.
You can use Test Clocks to advance time to test these: https://docs.stripe.com/billing/testing/test-clocks
so Stripe's preference would be to rely on subscription schedules entirely becuase you can benefit from some of the built in features
That is what I assumed would be the case ...
That depends on what features you're referring to here. Can you be more specific please?
using subscription schedules we wouldn't have to manage a future task to downgrade users for example
we would set the subscription schedule and it would be taken care of
Hi there, I am taking over for my colleague who had to step away.
Yes that is correct. Of course you can do it on your own but that requires more manua work from your side. With subscription schedules you would leave that flow to the schedule
just to confirm though -- is there any downside to releasing a schedule that's active, in cases where there is no future phase?
I am trying to think of a downside but not sure if i can find any. It all depends on your business flow. Just to make sure you keep an eye on those released schedule I would recommend listening to the subscription_schedule.released webhook event
https://docs.stripe.com/api/events/types#event_types-subscription_schedule.released
okay thanks ! just feels like a mountain of code to write to make this change even if it's ultimately for the better
It's hopefully a one time investment compared to ongoing subscription maintenance.
Yeah, no problem. Always happy to help.