#mudassir.dev

1 messages · Page 1 of 1 (latest)

delicate remnantBOT
timber gulch
#

Hi there!

#

Can you share the event ID (evt_xxx)?

odd hornet
#

sure

#

evt_1NUnxMJDsF3FhY2azj5IhjkM

#

Its triggerig twice and causing error

timber gulch
#

From our end this event was only send once to your endpoint.
Can you share the events ID from your screenshots? I'm guessing they are different.

#

I had a look at your account, and I can see evt_1NUnx2JDsF3FhY2ao8wIzN9N was sent twice, and every time your server responded with a 400 error.

#

So you need to check your server logs, and make sure you return a 200 response

odd hornet
#

why was it sent twice

#

I only triggered the event once

#

that's my root issue

timber gulch
#

Which event are you talking about exactly? Can you share the event ID?
The one you shared at the beginning (evt_1NUnxMJDsF3FhY2azj5IhjkM) was only sent once.

#

The one I found (evt_1NUnx2JDsF3FhY2ao8wIzN9N) was sent twice becayse your server didn't respond with a 200 response.

odd hornet
#

"evt_1NUnx2JDsF3FhY2ao8wIzN9N",

#

This one

#

why was this triggered

timber gulch
#
  • The event was triggered on 2023-07-17 at 09:42:44 UTC
  • A few seconds later it was send to your webhook endpoint, but your server responded with a 400 status
  • So Stripe re-tried sending you the event, and your server responded again with a 400 status
  • So in the near future Stripe will try again to send that event
    And you can learn about the try logic here: https://stripe.com/docs/webhooks/best-practices#retry-logic
#

The issue comes from your webhook endpoint. You need to check your backend logs to understan why you return a 400 error.

odd hornet
#

I wil have a look thanks

delicate remnantBOT