List what was delivered where, and how it went

Every time Commune handed one of this newsletter's events to one of its destinations, newest first: which event, which destination, what came back, and whether it was a first try or a retry. Needs sending: read.

This is the answer to "my endpoint never received that event". Each row names an event_id, which is the same string the consumer sees in the Commune-Event-Id header and in the envelope's id, so a line in your own logs and a row here can be matched up. ?event_id= goes the other way: give it an id and get every attempt at delivering that one event.

An event is delivered once per destination, so one event with three destinations produces at least three rows here. ?destination_id= narrows to one of them, and ?status=failed is the usual first read.

A retry is a new row, not an edit. attempt is 1 on the first try and one higher on each retry, and the delivery service retries a failed delivery on its own with backoff, so a row with status: failed is not yet a lost event. manual says whether somebody asked for the attempt rather than it being automatic.

Attempts are recorded shortly after delivery rather than instantly, so an attempt made a moment ago may not be on this page yet. Read again rather than concluding nothing was tried. The log is a recent record rather than an archive, so keep anything you need to hold on to.

Two things are never returned: whatever a destination authenticates with, and the response body your endpoint answered with, since a refusing endpoint routinely echoes the request back inside it, headers included. response_status stands in for the body, and the delivery portal has the rest.