#charun

1 messages · Page 1 of 1 (latest)

timber stirrupBOT
scenic dove
#

Hi can you share the subscription schedule id?

pure yacht
#

yep it's "sub_sched_1MCm8vHHHT1qJ1rw4J1jmy3a"

scenic dove
#

Thanks. Looking

civic birch
#

Hey, it looks like this is a limitation of how subscription schedules work at the moment. It looks like this may be able to be enabled for your account but I need to look a bit further in to it

If not, this is possible to do if you create the subscription first and then create a schedule from that subscription and add the second phase. So that might have to be the workaround if this can't be enabled for your account

#

Unfortunately still having trouble finding clarity on if this can be enabled. If you are interested in switching your schedule's anchor behavior from what it is now to backdating the start date as you initially expected, we can create a ticket to enable this if possible

pure yacht
#

it seems like it was possible to do that when we migrated users from our legacy system back in August. Since then, we accidentally set the billing cycle anchor back to null, and this question comes up while trying to recreate the migration in test mode. Is it possible that that option was disabled between August and now?

civic birch
#

I think I may have misunderstood your question, this isn't something that would have been enabled back then. Do you have the ID of the other subscription that that happened for?

pure yacht
#

for cus_MB5ChRcLeILF6p, we migrated them in August. In November, we applied a coupon to the next phase of their subscription, but in doing, that, we omitted the billing_cycle_anchor field in the body of the request, so it was set to null. Right now, the invoice is anchored to the date that the subscription started

sand bobcat
#

👋 stepping in as Pompey needed to step away

#

Okay apologies @pure yacht

#

So you want to know why the billing_cycle_anchor is set to 8/10, correct?

#

Have you used a test clock to actually test this out?

#

My understanding here is that you are just getting thrown off by the Dashboard preview which doesn't take into account the next phase of the Subscription

pure yacht
#

I tried creating another customer in test mode and going through the same process of creating a subscription schedule, but now I'm getting the correct next invoice date for cus_MwgyZWSO5kRWFU. So I guess my question now is, why is cus_MwfMbvHA9iisbA next invoice anchored to the subscription, while cus_MwgyZWSO5kRWFU is anchored to the phase start date?

sand bobcat
#

Looking

pure yacht
#

The only difference I can see is that the first customer's first phase ends in 2023 while the second customer's first phase ends in 2024. Would that affect the next invoice date?

sand bobcat
#

No it shouldn't really

#

Can you run a test of updating the Sub Schedule on your test customer and adding a coupon like you did in the initial example?

pure yacht
#

which customer do you want me to apply the coupon to?

sand bobcat
#

Ah! So sorry @pure yacht I think I misread the dates initially

#

For your first Sub, the end date of the first phase is in 2024 after the first cycle, right?

#

Like the first cycle is the normal 1 year from Aug 10, 2022 - Aug 10, 2023.

#

Then the next cycle will be shortened because the Phase ends on June 26, 2024

pure yacht
#

so yes, the end date of the first phase is in June 2024, but we expected the invoice to be anchored to the June date too. Is that not the expected behavior?

sand bobcat
#

Oh okay well that's the difference with the Subscription Schedule update that you did that I referenced above

#

That removed your initial backdated start date

#

And reset the billing cycle anchor

#

That is why you are seeing your testmode one with the correct March 1 billing cycle anchor

#

Since you didn't update that one to add the Coupon

#

Your update for the Sub Schedule set your start_date to 8/11/22

pure yacht
#

yes, but we've been creating fresh test mode customers and even without applying the coupon, we're still seeing that the invoice is anchored to the sub start date

sand bobcat
#

That wasn't what happened in the example above, no?

pure yacht
#

cus_MwfMbvHA9iisbA

#

this one has the sub start date as the anchor for the invoice date

#

we thought the anchor would be the phase_start, which in this case is 6/27/22

pure yacht
sand bobcat
#

Okay let me check on something, one sec.

sand bobcat
#

Okay

#

Finishing up some testing

#

Alright so a few things here

#

First, for cus_MwgyZWSO5kRWFU this looks to be due to the Test Clock frozen time that is set

#

So that is a test clock bug that seems to be manipulating the upcoming invoice to set the billing cycle anchor to that frozen time date

#

I'll report that internally

#

Second, I found a ticket internally that explains that Schedules that create Subscriptions currently do not support backdating the billing cycle anchor.

#

This is a gap that is being worked on but there is no timeline for it to be added/fixed currently.

#

So that explains why you aren't seeing the desired backdated billing cycle anchor for the upcoming anchor

#

The workaround in this case is to create the Subscription first with a backdated start date

#

Then you attach a Schedule to the Subscription

#

So that the Subscription does have the correct backdated start date and the initial billing cycle anchor is set correctly