mehdi_best-practices

[timid shore]

👋 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/1265263069337223210

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[bleak kernel]

hi! yes, that's expected, you have to manually update each subsequent phase so changes made don't get overriden, it's a known pain point in the Schedule API.

[azure gull]

Oh okey, I see, thank you!

Another way I thought about it is use Subscription Schedule update instead of updating the subscription when upgrading it.
But Subscription schedule doesn't have an equivalent of payment_behavior : pending_if_incomplete, right ?

Again, thank you very much!

[bleak kernel]

Another way I thought about it is use Subscription Schedule update instead of updating the subscription when upgrading it.
yes, you can do that too .For clarity if you update a Subscription that is managed by a schedule, that does "write back" to update the current phase of the schedule as well so you don't have to do the update via the Schedule; but future phases don't change, which is the issue you're running into.

But Subscription schedule doesn't have an equivalent of payment_behavior : pending_if_incomplete, right ?
yes, correct. I know it's messy but probably the best option is updating the subscription, and then when your webhooks detect the pending update went through and the subscription has updated, make an API call to update the subsequent phases of the Schedule.