developer_bob

[willow gate]

Can you share a CLI screenshot or paste the output?

evt_1OPNDn2nDnAL4MMhoStqBnnC is definitely a customer.subscription.created event

But when that fires there'll also be an invoice.created event created in parallel. So could be that the layout of the CLI output is just confusing and you're looking at the wrong ID/line

[limpid cairn]

Certainly, it looks like this on my end. No mentjon of customer.subscription.created in that output.

[willow gate]

The IDs are clearly different though. invoice.created ends in JBTq

I think the issue is that your endpoint sent 500 response to the customer.subscription.created to it's not logged

[limpid cairn]

Ah right, since "evt_1OPNDn2nDnAL4MMhoStqBnnC" is under "invoice.created" I thought the 500 was sent in response to that event.

[willow gate]

Well directly under that you can see the 200 response for JBTq

[limpid cairn]

Ah ok, so the 500 was sent right after the 200 in response to invoice.created, but is not related to that event?

[willow gate]

No, you can see the evt_xxx IDs are different

My guess is somewhere in your terminal logs there's mention of customer.suybscrition.created event, it's just cut off in the screenshot

And then eventually your endpoint responded with a 500, it just happened after the other events were handled sucessfully

[limpid cairn]

Yes, sounds like this is exactly what happened. Thanks a lot for your help! I was just confused 🙂