#paramnesia2416
hearty saddle
Hello
deft lotus
Hi bismarck
hearty saddle
Yep canceled_at is specificall when the Subscription was scheduled to be canceled in the future (see: https://stripe.com/docs/api/subscriptions/object#subscription_object-canceled_at) so this makes sense
You want to either focus on cancel_at
analog lavaBOT
hearty saddle
Or the ended_at works too
deft lotus
If ended_at works - then that's what I'll use. I just don't see why canceled_at would be a timestamp so very close to the subscription->created_at property. That seems like I've done something wrong.
It's not when it was originally intended to be cancelled ... it's shortly after the Sub was created.
sudden moss
Yeah if you use a schedule it'll align to when you create the schedule
It reflects the timestamp that you set the subscription to cancel
Not the timestamp the subscription will actually be canceled at
deft lotus
O.k. - will try and get my head round that. Natural assumption would be for subscription->canceled_at to reflect the timestamp at which it was canceled; either the schedule or the subscription .. but not the creation time. Don't think I get it, but will just use ended_at. Thanks both!
sudden moss
No problem