#thomasst-sub-schedules
strong fox
hello, can you share an example request? that way I can see what you passed and what you got back
low pebble
Are you able to pull requests for sub_sched_1LZhNGBSqAkKUXpQmeL4RQa6 / sub_1LZhMeBSqAkKUXpQ5Wf1XYDg from the past few minutes?
strong fox
having a look, do you also have the request ID from the request you made to modify the Schedule?
low pebble
req_fXaFwK9TbjRGvp
The product quantity was at 1 and had two phases (one to set it to 2, one to set it to 3). I then changed the product quantity to 4 right away.
In the request I gave you I tried cleaning up the old subscription schedules by only posting the new ones.
So I'm surprised it still returns old phases where the quantity is 1.
low pebble
@strong fox let me know if you have any further thoughts on this, thanks 🙂
strong fox
yeah I looked at it seems expected behavior for now, you are expected to see the older phases in the API request, you just need to look at the ones that are applicable to you now aka ones that are after current_phase.start_date top level on the SubSchedule
so you should see all the phases on that SubscriptionSchedule
low pebble
Thanks. And when modifying a subscription schedule it's safe to either 1) post back old phases unchanged, or 2) not post back old phases? As in, either way they will remain on the schedule, right?
Similarly, could I exclude posting back the current phase if I only wanted to modify future phases on the subscription schedule?
Sounds like the answer to my very last question is false since I'd then get "You can not modify the start date of the current phase."
earnest eagle
both work