#stephen-crosby_subscription-pending-updates
hasty mulchBOT
👋 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/1471555646297210933
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dawn remnant
Hello 👋
You are attempting to follow this guide, correct?
https://docs.stripe.com/billing/subscriptions/pending-updates#update-subscription
daring swift
Exactly
dawn remnant
You are usign the plan parameter. That is not supported. You should use price instead
We list the parameters that support pending updates here: https://docs.stripe.com/billing/subscriptions/pending-updates#supported-attributes
daring swift
Ah you're right. I didn't notice this. Is that the only thing wrong?
dawn remnant
Everything else looks good to me. I recommend you test it though. It is a shame we don't provide some kind of feedback though
daring swift
Ok. Now I have passed price, but still don't see the pending_update. Can you look at this request? req_qyqx0CP1j2rTUX
dawn remnant
Hmmm... I'm looking at the subscription and it doesn't look like you actually made any changes. The subscription item si_TxzdbIcvAAp9qv currently uses the price price_1QhIvVB8wovMzpKJDPUVRIcL with a quantity of 1 and the Subscription is active (not in a trial).
daring swift
Ok. How about this one then: req_cEQcekNQV4eefN this request I think results in the event which changes the price evt_1T03sWB8wovMzpKJobwfb0Zv
dawn remnant
Based on my read of the first section of our doc: https://docs.stripe.com/billing/subscriptions/pending-updates, that suggests we won't generate pending updates
Taking a look at the latest request
Oh oh oh oh...I think I see the problem.
Maybe...
daring swift
I hope so. I'm at a loss
dawn remnant
I did notice you were on a very ancient API version: 2015-01-26. I'm looking through our changelog to see if pending updates were a breaking change released sometime later.
Has this ever been successful for you?
hasty mulchBOT
stephen-crosby_subscription-pending-updates
daring swift
No. We're exploring the idea to try it for the first time
dawn remnant
Gotcha. It might require upgrading API versions but that is a big undertaking so let me verify that first.
hasty mulchBOT
vivid swallow
hello! fyi i'm taking over for snufkin, give me a bit to catch up
and apologies in advance, 2015 is many many versions ago so it might take me a bit to figure out what could be different here 😅
@daring swift what happens if you also pass proration_behavior: 'always_invoice'?
IIRC this type of update should only trigger pending updates when it also generates an invoice and the payment fails
so to test this properly you would need to
- attach + update the default payment method of the test customer to one that will fail (
4000000000000341/pm_card_chargeCustomerFail) - when you update the subscription, include
proration_behavior: 'always_invoice'
ok yes i just tested that flow myself on your API version and it looks like it worked
vivid swallow
ok great! does that resolve things for you?
daring swift
yes. i appreciate your help