#charun
arctic nymph
copper bramble
Hey there
Hmm can you give me an example where it isn't changing when you have it set for phase_start?
That should ensure that it resets at the beginning of the phase
thorny adder
Hi! So basically when I update the subscription schedule so that the current phase has a billing cycle anchor of 'phase_start', the next invoice date is based on the date that the subscription started, and not the start date of either the current or next phase
copper bramble
When you perform this update do you want the billing cycle anchor to reset immediately to when you make the update?
Like affect phase 0?
thorny adder
Yep
thorny adder
I'm just pulling the subscription schedule, and changing the billing_cycle_anchor field of current and next phases to phase_start, then using the subscription schedules API to update the phases by passing in all the phases
this is what the update request looks like. Was wondering why the next invoice isn't tied to the start date after this update
copper bramble
Can you give me the request ID (req_xxxx) for that update so I can look at the specifics
There are a lot of variables here
thorny adder
yep, it's req_GZR3k4EK8srgY6
copper bramble
Thanks, give me a couple
gleaming raft
Hi there. Taking over for bismarck as they have to step out. I'm looking at this rn
thorny adder
Sure, thanks!
gleaming raft
Ok just to confirm. You're expecting the next invoice to be 8/11/23 instead of 8/10/23? Is that the issue?
thorny adder
Hmm, just realized that that was not the best example. Could we try looking at req_ASKTS9SplgD00d instead? Same issue, but more clear here. The next invoice for this customer is still 8/10/2023 even though the phases in the schedule suggest that it should be in March, since I just updated the billing cycle anchor to be phase_start
gleaming raft
Ok thanks looking
Getting a colleague who's more familiar with this flow to look right now
Will update you
thorny adder
Alright, thanks
ember saddle
Hi there! Stepping in for my colleague who had to hop out.
Thanks again for the example. This looks to be a bug, unfortunately.
We're sharing this with the engineers on our end but, going forward, you may want to create these as backdated subscriptions and then create a schedule using the existing subscription.
thorny adder
Hi!
Thanks for getting back to me on this and for sharing with the engineers.
Yep, initially this was created as a subscription then a schedule was created on top. I was trying to apply a coupon to the next phase, but didn't supply the billing_cycle_anchor in my request, which is why it was null. This was an attempt to fix the billing_cycle_anchor for those subscriptions, and makes sense that it's a bug. Is this thread the best way to get further updates on this?
(CC: @green fable )
ember saddle
Got it. Not exactly, as these threads are short lived. Could you write in to our support team at https://support.stripe.com/?contact=true and let them know you were chatting on Discord with roadrunner?