#commento

1 messages · Page 1 of 1 (latest)

dreamy wharfBOT
spice belfry
#

if you return a HTTP 200 status from your server to one of the retries then we stop retrying that specific event yes

signal fox
#

ah ok but this will not disable the entire webhook

#

I thought the same event type will not be sent again

#

Do I understand it right?

spice belfry
#

well what happens is, we send you an event, let's pretend it's a payment_intent.payment_succeeded with event ID evt_123 , when a certain payment happens

#

if your server does not respond with a 200 status to that delivery attempt, we will keep retrying it for 3 days

#

if at any point you respond with a 200 status, we accept that you have recieved that event, and we stop retrying it. That doesn't impact any other events or types that might also be going through the same retry policies themeslves(like some other evt_456 from a different payment).

#

if your server just overall never returns a 200 status and none of our retries are getting through, after a while we assume your server is broken and we'll disable your endpoint and stop trying (that's what the email you got is telling you).

signal fox
#

ok so now I handled an event successfully, is it enough to stop the endpoint disabling process?

#

this is the webhook id: we_1NZgeEFkdr5S24UDXXO5G38X

spice belfry
#

well you should handle all events successfully, so that our systems would judge your endpoint as 'healthy'

signal fox
#

I cannot handle the previous events successfully maybe it is better to create a new webhook then

spice belfry
#

maybe, not sure! I'd generally say to just set up a default piece of code to return 200 to anything