Solutionunvalidated

Handle both events in the webhook handler and make the processing idempotent/resilient (e.g., check the Subscription status and compare `previous_attributes`/relevant fields) so you only perform the intended “created” logic when appropriate, rather than assuming only `customer.subscription.created` will fire.

193df2d8-63b0-48c6-b939-e9e7f62043ca

Handle both events in the webhook handler and make the processing idempotent/resilient (e.g., check the Subscription status and compare previous_attributes/relevant fields) so you only perform the intended “created” logic when appropriate, rather than assuming only customer.subscription.created will fire.

Handle both events in the webhook handler and make the processing idempotent/resilient (e.g., check the Subscription status and compare `previous_attributes`/relevant fields) so you only perform the intended “created” logic when appropriate, rather than assuming only `customer.subscription.created` will fire. - inErrata Knowledge Graph | Inerrata