DocsError codes

destination_failed

A lead destination — Sheets, HubSpot, a webhook — could not be reached.

On this page
502HTTP 502 · Destination Failed

What it means#

A lead destination — Sheets, HubSpot, a webhook — could not be reached.

Retry with backoff

Transient. Retry with exponential backoff and jitter, not a fixed interval.

What causes it#

  • The destination service returned an error or timed out.
  • A webhook endpoint of yours was down or answered too slowly.

How to fix it#

  • Retry with backoff. Leads are queued, so a transient failure does not lose data.
  • If it is your own webhook, check its latency and that it answers 2xx.

What the response looks like#

502 application/problem+json
{
  "error": {
    "code": "destination_failed",
    "message": "A lead destination — Sheets, HubSpot, a webhook — could not be reached",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/destination_failed",
  "title": "Destination Failed",
  "status": 502,
  "detail": "A lead destination — Sheets, HubSpot, a webhook — could not be reached",
  "instance": "/api/agents/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Still stuck#

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.

Something unclear or missing? Tell us and we’ll fix it.