#tom_unexpected
strange slateBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1470735130950631547
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
echo ocean
The unexpected behaviour is when the error is thrown saying the max trial period is 2 years, it deletes the scheduled subscription.
strange slateBOT
weak fossil
hey there 👋 taking a look at your example now
echo ocean
Thanks!
weak fossil
so the max trial period is two years, that's correct
looking at this request, it seems to be an attempt to create a subscription (i.e. not an update to an existing schedule), and it's failing due to the trial_end value being above the two year limit
you mentioned you're editing an existing subscription schedule - are you able to share the ID for that schedule? (sub_sched_123)
echo ocean
The subscription creation was triggered due to modifying the scheduled subscription in the fashboard
It's failed ungracefully here
Let me look
sub_sched_1SzE6SEVrnv1gjeaNT4VYz2T
weak fossil
thanks
echo ocean
(Also the 2 year trial limit differs to the scheduled max trial limit of 20 years - might need clarification in docs on this).
weak fossil
yeah this all seems a bit messy honestly, I'm surprised that the dashboard request comes through as a fresh subscription creation request rather than an update to the schedule
echo ocean
It's not a problem my end, but just thought I'd raise it to you guys as I think it's not up to the standard I see with everything else 🙂
weak fossil
I'm still looking into it, but are you able to share a quick breakdown of your use case (i.e. the steps you're taking why you're following this flow?)
ah ok, if this isn't blocking you then I can try to reproduce and take the feedback internally
echo ocean
Yes not blocking so don't worry
Use case is if we take payment offline (EG a cheque or PO) we schedule a new plan for the customer who sometimes choose a future start date.
I'm building a new system, but I am just testing what would happen if the customer wants to pay for even more time for the scheduled subscription, or if they want to move the start date.
weak fossil
ok, thanks for flagging!