#jscheel
unkempt elk
unkempt bloom
Hello there
hardy anvil
Hello @unkempt bloom !
I think I've made schedules way more complicated in my mind than they need to be 🤦♂️
unkempt bloom
Well, to be fair, schedules are kind of complicated.... which is necessary to give the level of customization that they provide.
Overall though let's walk through it together.
You should still specify quantity, otherwise if I remember correctly it is going to default to 1
hardy anvil
ahh, ok
unkempt bloom
The best thing to do with schedules is to use them alongside a test clock
Have you played with test clocks yet?
unkempt bloom
Yeah it is the best way to check that your schedule is going to behave how you expect.
We can discuss things but honestly you will get the best sense of how this works by just creating a few schedules and advancing the test clock
I'd recommend doing that to start with and then if you have any specific questions or are confused by anything we would be happy to help.
unkempt bloom
Sure
hardy anvil
am I correct in saying that any change to the underlying subscription, if it currently has a schedule associated with it, needs to happen on the "current phase" of a schedule?
and that "current phase" is defined by the bounds of the start date and end date of the current_phase key on the schedule?
unkempt bloom
Yes overall that's correct. You can either pass the current phase as phase 0 when updating a Sub Schedule in order to update the Sub for the future. Or, you can update using phase 0 to update the Sub immediately.
hardy anvil
ahhh, so I can always assumes that phases[0] is the current phase?
welll......
unless it has a start date in the future
right?
unkempt bloom
Sure thing