#cheng_api
grizzled valveBOT
👋 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/1327079143644463265
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
torn shard
Hi, there, did you have a similar request that worked in the past to compare?
In other word, did you notice this changed recently?
hollow helm
Hi Orakaro, thanks for replying. We only started using subscription schedule a few days ago, before that they're all regular subscriptions, and an example log is req_j9Muz5EZ70vR63 for the same customer using normal subscription.
torn shard
Sure, thanks and looking closer...
This is difficult to follow since there are a lot of similar requests changing the schedule
To simplify maybe it's better to reproduce the issue in Test mode 🤔
ie. req_mZKvYQt2Kl5cY4 is on 2025-01-08 03:59:30 UTC but there were req_KMinOP8NZJq9F6 (before) or req_88N4h8MgBgug5G (after) or req_qJ1o5KbX06JQJu (after) or many more, all were changing the schedule
hollow helm
Sorry for that. I just sent a test request req_DISMX3sdIh8WBk, the customer was on a scheduled subscription with quantity 5, and we sent that request to change the quantity to 6, then the changes are prorate in the pending invoice items list which we'd like to invoice immediately
torn shard
Ah I see. The proration_behaivor here, inside the phase level only affects "when transitioning to this phase". But this phase is already on so it has no effect. You may want to try the proration_behavior on upper level
Whether the subscription schedule will create prorations when transitioning to this phase. The default value is create_prorations. This setting controls prorations when a phase is started asynchronously and it is persisted as a field on the phase. It’s different from the request-level proration_behavior parameter which controls what happens if the update request affects the billing configuration of the current phase.