#vashist_api
still baneBOT
👋 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/1389552882902241372
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- vashist_api, 4 days ago, 56 messages
boreal crescent
Hello 👋
What is the desired end state of these subscriptions?
The problem here is that when you modify the Subscription directly that is controlled by a Subscription Schedule, it will cause side effects like this
In this request you paused the Subscription itself.
tribal tartan
Let me check
ok I have 2 questions -
- So how to correct the schedules for this particular subscription - we have tried possible ways and it always says the start date cannot be changed for past phase (because, both phases are having the same date)
- How to pause a subscription with schedules to avoid phases with same start date
boreal crescent
For 1. What is the desired end state?
tribal tartan
To update the schedule end behavior as cancel, update the end date of the active phase to 1770335999 and proration behavior should be None while updating -
In short this is the api request that was made
{
"end_behavior": "cancel",
"phases": {
"0": {
"currency": "usd",
"default_payment_method": "pm_1QePVCI5vSu94Gk8HcrgLZoV",
"end_date": "1770335999",
"items": {
"0": {
"plan": "price_1QHi2WI5vSu94Gk8y5Iji9gn",
"price": "price_1QHi2WI5vSu94Gk8y5Iji9gn",
"quantity": "1"
}
},
"proration_behavior": "none",
"start_date": "1736205279"
}
},
"proration_behavior": "none"
}
boreal crescent
Which request ID corresponds to that request?
tribal tartan
req_Z9xhfYzH80K9oV
still baneBOT
tribal tartan
Also, this issue is not happening for a similar pause request submitted for another subscription - sub_1R7gfMI5vSu94Gk82WVWkLFS; In this case, the phases are correct i.e., the 2nd phase start date same as 1st phase end date
acoustic rampart
Yeah we think there's a specific issue with sub_sched_1QePVPI5vSu94Gk8XeYC1SdN. It's in a weird state with multiple phases with the same start_date which overall should be impossible
That is causing the update requests to error, like your example
tribal tartan
ok, is it possible to get the data fixed? I think we might have a few more such errors, but this one is priority
acoustic rampart
Sure, but you'll need to write in to our team and we can work to prioritise that with the Billing team
still baneBOT
Hello @tribal tartan, we have sent you a direct message, please check it at https://discord.com/channels/@me/1389563658782375988
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
tribal tartan
These are the other 2 cases for which we have the same issue - sub_1QhcscI5vSu94Gk8xKcOKp4C, sub_1Qk7p4I5vSu94Gk8bhNPgoQK
Would you be able to fix them now? or would you require more time to look into it?
acoustic rampart
They'll require investigation yes. You can share all the context with me/my colleague via email
tribal tartan
ok, I assume you (or team) would reach out to me first by email because I only got a automated email and no reference numbers