Skip to main content

Delivery log

The Delivery Log has one row for each pair of an event and a subscriber: "event 812 to subscriber 3". It shows how many times the worker tried, what the answer was, and the last error. It is a read-only list.

How to open it​

  1. Switch to Enterprise. See Enterprise sidebar.
  2. Open Integration > Delivery Log.

The menu item is ent_event_delivery_menu. It opens the list ent_event_delivery_list_form. The card is ent_event_delivery_normal_form. The data object is integration_event_delivery (table enterprise.integration_event_delivery).

How a row is made​

When the delivery worker finds a new event and one or more active subscribers match it, it makes one row for each pair, with the status pending. The pair is unique (integration_event_delivery_event_id_subscriber_id_key). The worker then tries the delivery, according to the Delivery setting of the subscriber, and updates the row. See Event and delivery statuses for the values and the moves between them.

The list​

LabelColumnTypeFilterWhat it shows
IDidWhole numberNumberThe delivery id.
Event IDevent_idWhole numberNumberThe event, as shown in the Event monitor.
Subscribersubscriber_idWhole numberNumberThe id of the subscriber, not its code.
Statustransmit_statusText, up to 10 charactersTextpending, processing, sent or failed.
AttemptsattemptsWhole numberNumberHow many tries have finished.
Last Errorlast_errorTextTextThe error of the last failed try. Cleared after a success.
HTTP Coderesponse_codeWhole numberNumberThe HTTP status of the last webhook answer. Empty for in-house deliveries and for network errors.

All columns are read only. The only button is Refresh. Click a row to open the card.

The card shows the same fields, all read only, with no buttons: Event ID, Subscriber, Status, Attempts, Last Error, Response Code.

The columns transmit_batch, last_attempt, next_attempt and response_body are stored but not shown on this screen. transmit_batch and response_body have no writer in the code, so they stay empty. last_error for an HTTP failure holds HTTP {code}: and the first 500 characters of the answer body.

Not confirmed by code: how you go back from the card to the list (the card has no toolbar). See Event monitor.

What it affects​

  • Nothing by itself. The screen only reads.

Who can use it​

list_integration_event_delivery, get_integration_event_delivery and count_integration_event_delivery are open to the default roles ADMIN, MANAGER, OPERATOR and VIEWER (crates/services/app-server/src/web/rpcs/integration_event_delivery_rpc.rs:7). There is no method to change a delivery or to retry a failed one. In Enterprise only ADMIN reaches the screen.