Webhook not being triggered

[Gijs de Wit]

Hi there,

I have a question regarding your webhooks. We are working on an app that connects to Eventbrite using your webhooks. However, one of our webhooks seems to have stalled. I've read some things on this forum regarding webhooks being disabled after errors, but I don't know if this is the case for us as well.

The webhook id is `8720632` and the only errors are a few "408 Request Timeouts". We are using AWS Lambdas, which are started upon receiving a webhook trigger. Therefore they could take up to a few secs (~3s) before returning a (successful) response. 

Could you maybe check your logs to see what's going on for this webhook and why it is (supposedly) disabled?

Additionally, could you give some insights in the timeout the webhooks are working with?

Thanks

Kind regards

[nata...@eventbrite.com]

Hi Gijs!

Thanks so much for providing your webhook ID and helpful details for us to investigate! 

I looked into our logs and found that after a high volume of errors, your webhook subscription was temporarily disabled for 24 hours on 2021-07-06, then automatically re-enabled on 2021-07-07. We are looking to make the webhook subscription status available for you to see in cases like this, so I have noted your instance as a request for this functionality.

We enforce a 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. For more information and best practices, feel free to review our Webhooks Documentation here. 

Best,

Natalie