Broken or Disconnected HTTP Integration

Updated 2 months ago by Chloe Kesler

Why did my HTTP integration get disabled?

If you received an email saying that your HTTP integration was disabled then you're probably wondering

why.

It can happen for any number of reasons, for example: the service that's used in the HTTP integration is experiencing a downtime, there's latency issues and the HTTP requests time out.

In the video below you can see how you can track the details of the issue:

I fixed the problem, but it keeps getting disabled!

If your HTTP endpoint has intermittent issues we still try to send up to 100 HTTP requests to it. We generally keep retrying individual requests if there are timeouts for example. However, if 100 requests fail in a row then we disable the integration. This is done to prevent abuse of our systems (and external services).

The good news is that If a couple of requests succeed (Ex: HTTP response code 200) then we reset the failure count back to zero.

To illustrate this:

- 100 requests fail in a row -> integration gets disabled.

- 90 requests fail, then a number of requests succeed -> the failure count gets reset to zero.

This way some intermittent failures will not lead to deactivation of the HTTP integration.

Using Hookdeck (3rd-party) to instantly and reliably manage HTTP integrations

Hookdeck offers a complete infrastructure to reliably deploy integrations that make handling and managing incoming webhooks you receive from Gorgias simple. They offer built-in scaling, failure recovery, monitoring and alerting without provisioning your own infrastructure or deploying new code.

You can avoid having to build your own infrastructure to successfully act on every webhook we send. It's generally recommended to implement logic to queue and asynchronously process webhooks and Hookdeck is the fastest and easiest way to accomplish this.


How did we do?


Powered by HelpDocs (opens in a new tab)