6.2.2.20 FailedDelivery
6.2.2.20.1 Purpose¶
An event a subscription could not deliver after Pub/Sub's attempts. Every subscription sends its dead letters to one shared topic, marked with the subscription they came from, and access keeps them here for 30 days, so the owner sees what failed, with the last HTTP status, and can ask for a redelivery.
6.2.2.20.2 Questions it answers¶
- Which events did this subscription fail to deliver, and why?
- Was a failed event delivered again, and when?
6.2.2.20.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
subscription |
WebhookSubscription | 1..1 |
|
event_id |
string |
1..1 |
|
event_type |
string |
1..1 |
|
attempts |
integer |
1..1 |
|
last_response_status |
integer |
0..1 |
The HTTP status the address answered, for push. |
last_error |
string |
0..1 |
|
dead_lettered_at |
datetime |
1..1 |
|
redelivered_at |
datetime |
0..1 |
When the owner asked to deliver it again. |
event |
string |
1..1 |
The CloudEvent exactly as it was sent, in JSON, so a redelivery sends the same event with the same id; deleted with the row. |
created_at |
datetime |
1..1 |
6.2.2.20.4 Relationships¶
References
6.2.2.20.5 Rules & constraints¶
- An event that a subscription could not deliver after Pub/Sub's attempts. Every subscription sends its dead letters to the shared topic
platform.external.dead.v1; Pub/Sub marks each message with the subscription it came from, and access stores it here. - Rows are deleted 30 days after
dead_lettered_at.