webhook delay and 408 request timeout

[Sungah Kim]

Hi,

I set webhook on order.update.

Sometimes it came  right away, but sometime it delayed or even not fired.

And most of time it got 408 request timeout and re-Attempts several times, which caused multiply processing on my client side.

I know there are bunch of conversations about Webhook bug, is there any improvement on it?

[Natalie Blikslager]

Hello,

Sorry to hear you are experiencing troubles with your webhook. Can you please provide the specific event ID(s) returning a 408 request timeout error for your order.update action so we can look into the webhook logs? The webhook bug that was causing severe latency was resolved in March, thankfully, and we continue to monitor webhook performance!

Best,

Natalie

[Natalie Blikslager]

Hello,

I wanted to note here that we also recently implemented a new 3.5 second timeout on webhooks and your webhook will return a 408 error if you attempt to do too much synchronously on your end. It is best practice to return a 200 status quickly and do additional processing async.

I hope this is helpful!

Thanks,

Natalie

[Matthew Pfeiffer]

Natalie,

We are having a lot of 408s on our web hooks. It is my understanding that a WebHook should continue to attempt to connect at least a few times, before just giving up. Is that accurate? Any idea when those retry attempts should happen? And if they are in fact retried, should the WebHook show as having multiple attempts when I view them in the Eventbrite system ?   https://www.eventbrite.com/account-settings/webhooks/

When I look back at some of the 408s from a few days ago, they all show as 1 attempt. 

[Matthew Pfeiffer]

In case it is helpful, our WebHook is 8229542

[Matthew Pfeiffer]

Example from 9 days ago, only showing as 1 attempt. 

[Rohan Tan]

Hi Natalie,

I was wondering if the webhook timeout was still 3.5 seconds? 

As currently I return a 200 in about 2 seconds and it seems to still time out.

Best Regards,

Rohan