tobyschachman

[grizzled imp]

Hello! Are you starting the trial as soon as the subscription is created? If that's the case you're likely only getting an initial customer.subscription.created event right when the subscription is created

If you give me a specific example subscription ID I can take a closer look

[lean flower]

Thanks! Here's somebody who created a trial subscription sub_1NkoNZKu0hPlfmoHyHtlidM3

[grizzled imp]

Yeah it's exactly what I thought it was - the subscription was created immediately with a trial from the start so there was no customer.subscription.updated event because nothing about the subscription changed

I'd recommend also listening to the customer.subscription.created event as well

[lean flower]

I see. Thanks!

Can you explain why previously we'd get a created and an updated?

With non-trials?

[grizzled imp]

Can you share an example of one of those?

[lean flower]

sub_1NkwxqKu0hPlfmoHb4g5eDLz

[grizzled imp]

Ah I see what's going on - when Checkout creates a Subscription :
-> if it's trialing, no payment is needed so the Subscription can be created immediately in a trialing status
-> if it's not trialing, we need payment to be completed and the Subscription will have an initial status of incomplete until payment is done

For the non-trialing subscription once payment is completed that updates the Subscription to have a stastus of active which is why you get that additional customer.subscription.updated event

[lean flower]

This makes sense. Thanks!