#aliab-subscription-schedule

1 messages · Page 1 of 1 (latest)

grim flareBOT
boreal lynx
#

aliab-subscription-schedule

#

@fierce lion I recommend not using end_date at all here. Just let the phase 2 of the Schedule last the full period before release

fierce lion
#

Ok, the full period then ends up being end of current cycle right? Is there a limit to number of phases that can be there? In our system it is likely this will be happening a lot and so I felt just doing a short lived schedule would be better and we create a new schedule every time. So in this set up phases ends up being an array of 2 elements max.

boreal lynx
#

the max is 10

fierce lion
#

Ok, then I suspect there will be a lot more than 10 before current cycle ends. So probably releasing it 1 second later may be the way to go?

boreal lynx
#

I don't know if that works, I'd recommend trying in Test mode to confirm and make sure there's no issue or proration happening

fierce lion
#

For sure. I did test that and it is working great so far.

boreal lynx
#

sounds good so that seems like a good fit

fierce lion
#

1 more thing. If a subscription has phases: [phase 1, phase2] and lets say end_date for phase1 has passed, can an update to schedule be made where we update the phases to [phase2, phase3] or does phase1 have to stick around in that list since it was once a valid phase.

boreal lynx
#

you don't need phase 1 if it's in the past

grim flareBOT
fierce lion
#

ah ok ... good to know. Anyway ... thank you for the help