ben_api

[fierce wyvern]

👋 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/1425480879412740147

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[visual sparrow]

hey there!
When you created the schedule (from an existing subscription) the first phase had:

start_date: 1759602502
https://dashboard.stripe.com/test/logs/req_4KueWsxeDOPSEE

but now you are sending the update with the first phase using:

start_date: 1759606161
https://dashboard.stripe.com/test/logs/req_A2iaX8759nlHFZ

You cannot modify the start date of the active/current phase, you need to send the previous value

[stiff lintel]

how odd, they must be ended up mistmatched between stripe and our db...

let me validate

there seems to be some sort of dormant scheduel stuck that we have no record of from what I can see

req_pEJQnpPfSU66yV

I cant seem to release this from our end using the api

[visual sparrow]

Yea thats the schedule you were trying to update in the original request you shared

[visual sparrow]

Can you share a failing release request?

[stiff lintel]

ive managed to clear it, i had to dig through the logs to find the schedule id

thanks for poointing that out

oddly it wasnt showing in the stripe dashboard which is what confused me

[visual sparrow]

NP!

FYI if there's already an attached schedule that's also indicated on the subscription object itself: https://docs.stripe.com/api/subscriptions/object#subscription_object-schedule