#danboyle8637
twin rainBOT
Hello danboyle8637, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• danboyle8637, 13 hours ago, 23 messages
• dan-checkout-webhook, 1 day ago, 13 messages
sour bison
Hi there 👋 can you elaborate more on what you mean by this:
First, the customer.subscription.deleted event. When I fire a test with the Stripe CLI this event runs two times. The "stack trace" of events being fired only shows the event running once. What am I missing here?
Where are you seeing the event being fired twice, versus where are you seeing the event running once?
For the second part, yes, charge.dispute.created is the best Event type to use there.
regal kayak
Sure... my endpoint listens to the customer.subscription.deleted event and does some stuff so we know about this. When I run the CLI stripe trigger customer.subscription.deleted command the webhook is running two times.
In my terminal where I run stripe listen... it shows the events that fire in succession and in that list the deleted event is only listed one time.
sour bison
Hm, yeah, when I run stripe trigger customer.subscription.deleted, I only see one customer.subscription.deleted Event in the lines listed by stripe listen. So it's in the logs from your webhook endpoint that you see multiple Events with the same type hitting the endpoint? Did you capture the IDs of those two Events from one of your testing runs that you can share?