#Kain Stropov (Найрра)
normal tusk
Hey there. What is the behaviour you're expecting?
Can you share some object IDs? Perhaps of the Subscription?
royal sierra
I expect that user who pay for subscription make payment on invoice and only then price on subscription will be updated and we activate features on our product.
Or maybe subscription owner declined updating and we void the invoice. And subscription returns to initial price.
Currently I am working on test environment.
normal tusk
Can you share sub_xxx ID?
normal tusk
It's safe to share (nobody can use the object IDs without your API keys)
(can't really help much without that to understand what's actually going on)
dry canyon
you've made a whole bunch of changes to that subscription today. Which update was it exactly that did something you didn't expect ? https://dashboard.stripe.com/test/logs?object=sub_0KqEzAGqGd6PNpzDmNPTYXVl the exact request ID req_xxx of the change might help. Might also help if you do a fresh test with a brand new subscription in case there's a mix up since you make many updates with different parameters on that one.
royal sierra
req_dThOtKLkhmUuj3 - changing to collection_method to send_invoice
req_5MKaLp0i0kfnDA - changing price with payment_behavior = pending_if_incomplete and proration_behavior = always_invoice
dry canyon
I see! Yeah, unfortunately, the pending update feature doesn't really work with collection_method:send_invoice, it wasn't designed for that use case. It only works properly when using charge_automatically.
we actually need to change this feature to a) not create a pending_update on the Subscription and b) explicitly call this out in the docs, I'll bump the task internally. But sorry, this feature doesn't work for send_invoice, it simply wasn't part of the design of pending updates.