bipin6343

[somber gate]

but in current subscription i still go cancel_at_period_end false how to solve this?
Seems expected if the cancellation is to happen in the furture and not in the current period.

The Schedule will set cancel_at_period_end on the Subscription automatically according to the phases you've configured

[buoyant umbra]

so how can we update cancel_at_period_end of current active subscrtion schedule?

[somber gate]

Can you share some object IDs? sub_xxx would be good

You'd just set end_behaviour: 'cancel' I think: https://stripe.com/docs/api/subscription_schedules/update#update_subscription_schedule-end_behavior

[buoyant umbra]

sub_sched_1NSba4AXWAgH6foQFIM4eiC1

yes i've done same to cancel at period end but this won't change status

[somber gate]

Sure, it's because you have phases configured to run until August 11, 2024. So the schedule will 'end' then and once it ends it'll cancel the underlying subscription

You've got a single phase on the schedule, with a yearly item

[buoyant umbra]

yes, i go so it should be cancel_at_period end is true right ?

because i'm cancelling this at end

[somber gate]

Well the Schedule hasn't started yet, so there's no underlying Subscription

It's not due to start until August 11, 2023

Only on that date will the Subscription actually be created

And I imagine cancel_at_period_end will be true then

[buoyant umbra]

this is the active subscrption from schedule

the schedule subscription is already on active so i updated to cancel at end

[somber gate]

Ah, you're using a test clock

[buoyant umbra]

it shows correctly on stripe dashboard as above picture but not on api

yes i'm using test clock

[somber gate]

Yeah I guess the schedule sets cancel_at as opposed to cancel_at_period_end: https://stripe.com/docs/api/subscriptions/object#subscription_object-cancel_at

[buoyant umbra]

I think this is bug to be reported

[somber gate]

Sure, feel free to write in to the team: https://support.stripe.com/contact