charun | Stripe Developers | Page 1

earnest badgeBOT Dec 21, 2022, 7:04 PM

#

sullen birch Dec 21, 2022, 7:04 PM

#

this is happening in live mode

minor latch Dec 21, 2022, 7:04 PM

#

Taking a look now

#

That customer has an active subscription and I'm not seeing any events that indicate it was ever cancelled.

sullen birch Dec 21, 2022, 7:07 PM

#

this is the event that gets generated from the request evt_1MGoTmHHHT1qJ1rwr50LkICP

minor latch Dec 21, 2022, 7:09 PM

#

Yeah, if you look at that in the Dashboard you can see it still has status: active: https://dashboard.stripe.com/events/evt_1MGoTmHHHT1qJ1rwr50LkICP

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

sullen birch Dec 21, 2022, 7:10 PM

#

It seems like the cancelled_at field was changed when the metadata updated

minor latch Dec 21, 2022, 7:12 PM

#

Are you using a 3rd party plug-in anywhere that uses that metadata you specified?

#

It seems like you likely are, yes? I just updated metadata on my end for a test subscription and nothing happens to canceled_at or cancel_at

sullen birch Dec 21, 2022, 7:20 PM

#

We're not using any 3rd party plug-in for this, this is us trying to tag subscriptions to know whether they are from our legacy system

#

It just seems like users who have already cancelled in the past are getting their 'cancelled_at" date changed

minor latch Dec 21, 2022, 7:23 PM

#

Hmmm... Let me confer with a colleague real quick and circle back in case I'm missing something obvious. I'll circle back shortly

sullen birch Dec 21, 2022, 7:24 PM

#

Sounds good, thanks

minor latch Dec 21, 2022, 7:37 PM

#

So, to assuage any fears about what's going on, it looks like canceled_at is the only thing updating (which is a bug, it shouldn't do that when you're only updating metadata). canceled_at is just a timestamp that tells you when you updated the subscription to have a cancel_at time.

In this case, the cancel_at timestamp remains unchanged, so there's not material effect on your subscription behavior. It's just the canceled_at field getting updated incorrectly on our side.

sullen birch Dec 21, 2022, 7:42 PM

#

that makes sense. good to know that this only impacts customers who have already canceled and it's not setting any subs to cancel

#

should i email stripe support to get this officially tracked?

minor latch Dec 21, 2022, 7:48 PM

#

It's already being tracked and t is planned to be fixed in a future API version.

#

Going to bump the thread on my end to make sure there's an accurate paper-trail to get it the attention it deserves. You're not the only person to flag this bug unfortunately.

#charun