thomasst

[silver lark]

I believe it should, looking

[ocean moat]

Thanks, let me know

[ocean moat]

@silver lark Any further thoughts on this? If I modify the subscription and remove the coupon manually, I get both events, but if the coupon expires, I only get the customer.discount.deleted, is that expected?

[ornate swan]

Hi there 👋 taking over for @silver lark as they had to step away. They brought me up to speed on the issue though so I'll jump right in.

So far it looks like that is the expected behavior, but it doesn't actually make a lot of sense for the reason you already stated

Shouldn't it trigger both since theoretically the discount property changed on the susbcription?
Not sure if this is a bug or a shortcoming though, so I'll need more time to dig on my end. I'll circle back with more info as it becomes available

[ocean moat]

Thanks. When do you expect the info to be available?

[ornate swan]

Hard to say, but I'll likely know in the next 15 minutes if I need to upstream to the product team or not

[ocean moat]

Sounds good. But you're seeing the same behavior as I'm seeing right now, right?

[ornate swan]

Yeah. It doesn't look like customer.subscription.updated is firing at all, but I feel like it should

[ocean moat]

Yep, let me know if you end up reporting it upstream.

[ornate swan]

Hey @ocean moat, apologies for the wait. So it looks like this is expected behavior and the reasoning is that the discount hash is effectively only ever a Coupon object or a Discount object. When one of those objects changes, the sub-resource does not actually result in a change to the parent object, so no customer.subscription.updated event is triggered because (to Stripe's systems) the Subscription object is unchanged.

After a bit of deliberation, it seems this behavior will remain default (even though it seems a bit strange)