#midnight_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ 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/1394669142929576047
đ 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.
- midnight_unexpected, 3 days ago, 16 messages
hey there, taking a look at the example thanks
it looks like you made this change after the start date of the second phase, so it was not scheduled in the future was was instead in the past when you changed it
Based on the request time and the test clock time
I would suggest retrying you test sequence which the new phase start applied later/after the test clock time
I scheduled the change and then used the time simulation
Actually hang on, i misread something
Ah the phase change was in the future -- apologies, my mistake
But you set proration_behavior=none in the phases
What is the customer flow / payment pattern you're expecting/trying to achieve, exactly?
They should receive one bill, and it should be for the full amount of the NEW plan. They should maintain there same billing cycle.
So when they go to renew, there are switched plans and billed once
Ok, i think i see a flaw here -- you're setting phase boundaries that don't match your subscription period like you expect
ie, this is not true:
When you schedule a change in plans with a subscription schedule phase, at the exact time of the renewal
When you created the subscription, the current period end was 2025-07-15 18:44:10 (1752605050).
https://dashboard.stripe.com/test/logs/req_evEMutrWWkJrek
Adding the initial schedule didnt change anything: https://dashboard.stripe.com/test/logs/req_vu9HuIKXEqSznr
When you updated the schedule, you set the new phase to start at 2025-07-15 19:44:10 (1752608650), one hour after the renewal
https://dashboard.stripe.com/test/logs/req_sI6ik7QOenok7q
So what youre seeing then is the natural renewal for the original price, then another invoice/renewal for the new price
You need to re-test this with the phase transition set to match the existing subscription period end
I see, that hour difference is the issue. TY