#ilyshakr_api
opaque surgeBOT
👋 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/1509925785023156357
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
ashen sandal
Hi there, looking into this now
Do you have a request ID for the schedule update you tried with always_invoice? That would be the approach I would have taken, so I want to dig into the specific details of the request there
In this case always_invoice should be set at the top level of the update request, not inside the phase parameters, so that's something we would double check
lucid lagoon
Do you have a request ID for the schedule update you tried with `always_invoice`...
yes, req_T6cn0KIJZbQ1dx
ashen sandal
Yeah, you can see in that request you're setting the proration behavior of the phase, which is described here:
https://docs.stripe.com/api/subscription_schedules/update#update_subscription_schedule-phases-proration_behavior
Controls whether the subscription schedule should create prorations when transitioning to this phase if there is a difference in billing configuration. It’s different from the request-level proration_behavior parameter which controls what happens if the update request affects the billing configuration (item price, quantity, etc.) of the current phase.
In this case you want to set the proration behavior at the top level
lucid lagoon
yes, thanks, can you tell me is invoice supposed to be with "draft" status? i thought it should be "open"
ashen sandal
Looking into it, can you send me the invoice ID that you're looking at?
lucid lagoon
yes, one minute
"in_1TcRmH7P7nc4A1scJyYVshDO"
payment intent for this invoice is also null
ashen sandal
Still double checking the details, but I believe this is expected behavior - the invoice is created in draft with auto_advance=true, and will automatically finalize after about 1 hour. The payment intent is null until it is finalized. You can manually finalize the invoice if you want the payment intent right away
This behavior is described in our docs here:
https://docs.stripe.com/billing/subscriptions/subscription-schedules#managing
(not exactly the same situation as yours, but my understanding is that it applies here)