#tiem-schedule-iterations

1 messages · Page 1 of 1 (latest)

quasi drumBOT
foggy agate
#

tiem-schedule-iterations

#

Hey @steep ruin ! Having an exact SubscriptionSchedule id and the detailed info of what you didn't expect would help yes.

steep ruin
#

Hey @foggy agate ! The schedule id is sub_sched_1MPrVmIUwLvVicLYNtZeKRdh. I didn't expect a 10th and 11th payment of 713.17. I expected there to only be 9 instalments of 713.17. I only want there to be 9 instalments of 713.17 then the subscription schedule is released.

#

Sorry, log id is actually req_59OxBhJ3vKsn46

foggy agate
#

so you have a first phase with one iteration and then a second phase with 9 iterations right?

steep ruin
#

Yep that's right

foggy agate
#

so what's the exact problem?

steep ruin
#

I would expect the second phase with 9 iterations to only make 9 invoices... if I understand the concept of iterations correctly

#

Phase 1 did 1 iteration of a trial which is perfect, I expected phase 2 to do 9 only.

#

So the use case is: first instalment is a trial period (that is why phase 1 is a trial & only 1 iteration)... after the trial the customer 9 instalment (that is why phase 2 is not a trial & has 9 iterations)

foggy agate
#

ack looking

steep ruin
#

thanks

foggy agate
#

So the Schedule ended and released the Subscription

#

this is the Event that says "hey the Schedule was released and your Subscription will now go on as it was on the last phase of that schedule" basically

steep ruin
#

Ahhh okay, so then if I set end_behaviour to release, the 9 iterations will stop and the subscription will stay active after the release?

foggy agate
#

yes