#James-subscriptions

1 messages ยท Page 1 of 1 (latest)

twin tapir
#

๐Ÿ‘‹ happy to help

#

I'm testing this for you, just give me a sec

fringe berry
#

Thanks! I can provide some code snippets of my schedule update if it would be helpful

twin tapir
#

yes would be really helpful

#

are you on a metered subscription?

fringe berry
#

The subscription isn't metered currently

twin tapir
#

and you're using the same price id?

fringe berry
#

Yes, the price id is the same. Here is. the current code snippet ^

twin tapir
#

I don't think you need schedules for that

#

is there a reason why you are using Subscription Schedules other than to do this?

fringe berry
#

We use schedules to change prices at the end of the current cycle (monthly -> yearly). So we want quantity increases to occur immediately, but price changes to happen at the next cycle

#

When I attempted to increase the quantity of the current subscription outside of a schedule while a schedule was in place it could not apply the update due to the schedule being in place

pliant spindle
#

yep, if the subscription is managed by a schedule you're limited in the updates you can make

#

you can update the schedule object and adjust the current phase if you want to apply an immediate update though.

fringe berry
#

Thanks Karllekko, but can i send an invoice for the update immediately? AFAIK Stripe only allows the additional cost top be prorated onto the next invoice

pliant spindle
#

yep, proration_behavior:always_invoice should do that

fringe berry
pliant spindle
#

yeah true, we never added that to schedules(it's a new-ish param and they didn't prioritise adding it to Schedules when they added to Subs, I 'll raise the feedback again)

#

sorry!

fringe berry
#

Could you suggest a workaround for this issue?

pliant spindle
#

without that the only way to force an invoice for the proration would be to set billing_cycle_anchor:now as well but that's obviously quite different

pliant spindle
fringe berry
#

Okay, thank you. Is it possible to subscribe to this missing functionality to be notified once the issue is resolved? so that I can remove any workaround I do implement?

pliant spindle
#

not really no

fringe berry
#

Okay, that's a shame. Thank you for your assistance

pliant spindle
#

actually I looked and I think this is being released quite soon

#

I can't commit to specific dates but it seems like they're targeting the end of this month(but of course could slip). When it's available it will just be a new enum value you can pass to that phases.proration_behavior param