Skip to main content

Delivery Statuses

Every delivery has exactly one status.

StatusMeaningNotes
PENDINGQueued or in progress.The initial state, before the attempt resolves.
SUCCESSThe destination responded with a 2xx status.responseStatus, responseBody, and durationMs are recorded.
FAILEDThe attempt did not succeed.Caused by a non-2xx response, a connection error, or a timeout.

What counts as success​

Only a 2xx response (200–299) marks a delivery SUCCESS. Everything else is FAILED:

  • 3xx redirects — FAILED.
  • 4xx client errors — FAILED.
  • 5xx server errors — FAILED.
  • No response within the destination's timeoutMs — FAILED.
  • DNS, connection, or TLS error — FAILED.

See HTTP response codes for guidance per code.

Resolving failures​

Inspect the failed delivery's responseStatus and responseBody, fix the destination or downstream service, then replay the delivery. A replay creates a new delivery; the original FAILED record is preserved.