#stJanis

1 messages ยท Page 1 of 1 (latest)

mossy etherBOT
nocturne void
#

though all the expected functionality that needs to be triggered through webhook on prod, succeeds. but because of multiple Stripe webhook retries, I am getting different types of issues that needs to be addressed

mint crow
#

Can you share an example evt_xxx where this is happening?

nocturne void
#

sure thing, thanks!

#

evt_1MgnwaGyj7Gf2jeoRbeHARjo

#

just in case here is also an event id from test mode, which succeeds: evt_1MgnlyGyj7Gf2jeocOSiHWSB

#

so i am super curious to find out what am i missing here ๐Ÿ™‚

mint crow
#

Taking a look

#

Are you performing any custom logic/actions in your webhook handler? We expect a response within ~20 seconds of event being fired. Could it be that those actions are preventing a response within that expected timeframe and therefore timing out?

nocturne void
#

shouldn't be the case. in such case it would fail also on staging.

#

all the custom logic events are triggered almost instantly and related systems get's updated almost right away

#

this is also what puzzles me is that i can't replicate this error on staging

mint crow
#

Our general recommendation is to return a 2xx to us immediately on receipt of event and then carry out any actions/logic. In most timeout cases that is the root cause

nocturne void
#

thanks! i will try that, i am returning 2xx at the end of the event. so might be this fixes it

#

as long as you didn't see anything else obvious there, then i just keep debugging ๐Ÿ™‚ and will try your suggestion

mint crow
#

All I can see is that it timed out roughly ~20 seconds after we sent the event which is indicative of what I described

#

Your endpoint is reachable directly, I can ping it from our systems