#_greggles_
dark shellBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- greggles, 1 hour ago, 26 messages
- greggles-customer-pms, 21 hours ago, 27 messages
- greggles, 2 days ago, 28 messages
- greggles, 3 days ago, 21 messages
- greggles-subscription-bca, 3 days ago, 10 messages
south tinsel
Hm not sure off-hand. Let me ask a colleague
covert tusk
For context, I am only swapping out the price in phase[1]. Except for that, the original schedule is identical to the update.
trim sage
Have you advanced the test clock time to see what the actual invoice does?
covert tusk
I just did. The invoice was issued and paid at the discounted price of $33.46
trim sage
Looking at the new latest invoice in_1ODZktGxG8m2870UnBDyg6WR yes I see that
covert tusk
The following invoice looks like it will be correct
dark shellBOT
trim sage
ok, this is because of the previous schedule change to end_behavior: "cancel", here: https://dashboard.stripe.com/test/logs/req_bUI0oFcs1vOMqa
And not due to the phase price change
covert tusk
I'm resetting the end behavior to 'release'
trim sage
Yes but the proration was already created for the slated cancelation
then got attached to the phase change invoice
covert tusk
Proration behavior in the cancelation was set to 'none'
trim sage
If you retest the sequence without that end_behavior: "cancel", state, i would expect no proration for the phase change
No, that none is within the phase and does not apply to the cancellation itself
covert tusk
I'd like to keep proration behavior to none at every stage.
trim sage
(that was already the current phase, so that none would not be applied as part of a phase transition)
There is a top-level proration_behavior for this kind of change to the current phase:
https://stripe.com/docs/api/subscription_schedules/update#update_subscription_schedule-proration_behavior
If you set that to none you should be able to prevent that proration from the scheduled cancelation
covert tusk
Gotcha, thank you for clarifying. I'll try that and see.
trim sage
👍
covert tusk
Is that only for cancelation type behavior or should that proration behavior always be set at the top level?
trim sage
any kind of change to the current phase
covert tusk
If I always want it to set to none.
trim sage
the setting inside phases only applies for changes that happen during phase transition
covert tusk
Oh I see.
trim sage
There is no "sticky" proration setting, its request/change specific
Each update request and each phase change
covert tusk
Yes, so I'd set it to top level any time I update the schedule.
trim sage
If that's what you want, then yep