Routy

Outgoing webhook failed

Routy tried to send a conversion to one of your webhooks, and the receiving server did not accept it.

What it means

When a conversion happens, Routy calls each webhook you have set up for it. This issue means we reached out to the webhook's address and the call failed: the server replied with an error, timed out, or could not be reached at all.

The issue is about one webhook. Its message names the address we called and what went wrong, for example failed: Destination Server Not Found (HTTP 404). It is raised on the first failed delivery, not only after retries run out.

Why it happens

Most common first:

  • The receiving tool rejected the call. An HTTP 4xx reply such as 400, 401, 403 or 404. The URL path is wrong, a token or key in the URL has expired, or the receiving endpoint (a Zapier hook, for example) was deleted or turned off.
  • The receiving server had a problem. An HTTP 5xx reply, or the server took too long to answer.
  • The address cannot be reached. The domain does not exist any more, its DNS is broken, or its security certificate is invalid or expired.

If the issue instead says the URL itself is wrong (a placeholder we cannot fill), it is a different issue, Webhook URL is invalid, and the fix is in the webhook settings rather than at the receiving end.

What you can do

  1. Open the issue and read the address and the reason.
  2. Go to Events → Webhooks, filter Status to Failed, and open one of the failed deliveries. Delivery attempts shows what we sent and the exact reply. See Webhooks event log.
  3. Fix the cause:
    • For a 4xx reply, check the endpoint still exists in the receiving tool and that the URL and any key in it are current. If the URL changed, edit the webhook under Tracking → Webhooks, or on the traffic source's Webhooks tab. See Traffic source webhooks.
    • For a 5xx reply, a timeout, or a certificate problem, contact whoever runs the receiving server.
  4. Use Simulate on the webhook's row to confirm a test now goes through.

Failed deliveries from the last 10 days are retried automatically, about once an hour and up to 10 times each, using the webhook's current URL. So once the receiving end works again, recent conversions catch up on their own. You can also use Resend Webhook on a single delivery.

When it clears

It closes as soon as one delivery to that webhook succeeds. If nothing is sent to it for a while, it also closes 24 hours after the last failure. A new failure opens it again.