email.delivery_delayed | Nexiom Connect

Example payload

Example identifiers are shown below.

{
  "id": "00000000-0000-4000-8000-000000000001",
  "type": "email.delivery_delayed",
  "schema_version": 1,
  "data": {
    "id": "delivery_example",
    "message_id": "message_example",
    "recipient": "reader@example.com",
    "occurred_at": "2026-10-02T10:00:00.000Z"
  },
  "created_at": "2026-10-02T10:00:00.000Z"
}

When it fires

The provider reported a temporary delivery delay.

Event fields

data.idstring: Recipient delivery ID.
data.message_idstring: Message ID shared by its recipient deliveries.
data.recipientstring: Recipient associated with this event.
data.occurred_atstring: ISO 8601 timestamp of the delivery or engagement fact.

Handle this event

Keep the delivery pending and wait for a later outcome. Do not send a replacement just because delivery is delayed.

Verify the signature before reading the payload. Deduplicate by the envelope id, not the delivery ID: a delivery can have several different events.

Retrieve the email using data.id for its current state.