DocsError codes

notification_transient

Delivery failed for a reason worth retrying.

On this page
502HTTP 502 · Notification Transient

What it means#

Delivery failed for a reason worth retrying.

Retry with backoff

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

What causes it#

  • A timeout, a provider 5xx, or a rate limit.

How to fix it#

  • Retry with backoff.

What the response looks like#

502 application/problem+json
{
  "error": {
    "code": "notification_transient",
    "message": "Delivery failed for a reason worth retrying",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/notification_transient",
  "title": "Notification Transient",
  "status": 502,
  "detail": "Delivery failed for a reason worth retrying",
  "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.