#gabor
jovial rampart
Can you share the example Subcriptoin ID so I can take a look?
jovial rampart
When you used the test clock what timestamp did you advance to?'
ah I see it actually, nevermind - give me a few more min utes
primal pond
ok, thanks for looking into it!
jovial rampart
aha! found it - sorry that took a while
Turns out you didn't advance far enough in advance
At some point you updated that schedule sub_sched_1MpEIEIW2fFx6PmmxD2AeR1R to include some new phases which change the end date from 2024-01-25 -> 2025-01-25
Your test clock wasn't advanced to that date yet, so it didn't automatically release
primal pond
No problem at all, thank you for your help!
What I still don't understand is that the schedule object was marked as completed… while the subscription was still pointing to the schedule.
I switched the subscription from monthly to yearly only after the schedule finished.
Should the subscription's schedule parameter set to null automatically on release?
jovial rampart
What specifically did you check to see if the schedule object was marked completed?
primal pond
I ran stripe get sub_1MouxFIW2fFx6PmmpaD91uw6 in the terminal
…and stripe get sub_sched_1MpEIEIW2fFx6PmmxD2AeR1R
the latter, for the schedule object 🙂
…and checked the released_at and released_subscription params, that were both set (not null)
jovial rampart
Did you run those before you made the API request to release manually? Or after?
primal pond
before
then wanted to see, if running release request manually removes the schedule id from the subscription
jovial rampart
Do you mind trying this one more time but without running the release request at the end? I've tried reproducing this on my end as well and I'm not seeing the same behavior as you
primal pond
Not at all, I will try it again. I'll be back in a few mins.
dark glenBOT
primal pond
This will be the new subscription: sub_1MpFeYIW2fFx6PmmrOlLAqio
I've attached the schedule now: sub_sched_1MpFjAIW2fFx6Pmm21AR5OEq
Updated the schedule's middle phase by one more month.
I advanced the clock multiple times… until the schedule finished…
and everything works fine now
the subscription doesn't point to the schedule now
So, it's okay now. I have no clue what happened before.
Thank you again for looking into it!
jovial rampart
glad it seems like a false alarm! If you see it happen again definitely let us know
primal pond
I will, but hopefully I wont see that again.
I have one more question though: I'd like the schedule to be release right after the second phase, but still want the subscription to change back to the original state, as defined in the third phase at the moment. Is it possible to set the length of the third phase to zero for this?
jovial rampart
I need to head out, but codename_ducchess is around and can answer that for you
primal pond
no problem, thank you again @jovial rampart
uneven thorn
@primal pond You can just do 1 iteration of the 3rd phase and release after so it keeps going
primal pond
Hi @uneven thorn, I think that's what I'm doing currently, but it would be more ideal if the 3rd phase would be really short or zero length.
uneven thorn
You should be able to set end_date and just make it really short
primal pond
It's because I'm using this schedule to give free months as referral rewards to our users, and while the schedule is on, the second phase can be extended by one or more months.
1s might be a solution, it just shifts the anchor a tiny bit.
Otherwise I would need to remove the current schedule whenever the third phase is running and new referees arrive (extending the reward period).
uneven thorn
Yeah try with 1s
primal pond
Okay, I will. Thank you. 🙂