This page lists all webhook notifications produced by the source apps connected to DyXit, together with their delivery status. Use it to monitor deliveries, understand a failure and, if needed, re-send a notification.

Reading the list

Each row represents one notification. The main columns:

• Source App: the source app that raised the event.

• Event Type: the type of event notified.

• Correlation Ref: a readable reference identifying the item concerned.

• State: the delivery status (see below).

• Attempt: the number of attempts already made.

• Last Error: the reason for the last failure, if any.

Example: an invoice received through iopole shows up with Source App = iopole, Event Type = EDOCUMENT_RECEIVED, and, in Correlation Ref, the document number (e.g. IOP-INV-4183054). If several destinations subscribe to that event, you will see one line per destination.

Possible states

StateMeaning

PendingWaiting to be sent.

ProcessingBeing sent.

Done (green)Delivered and acknowledged by the destination system.

Failed (orange)Temporary failure; will be retried automatically.

Dead Letter (red)Final failure after all attempts; needs review.

Available actions

• Requeue: puts a notification back in the queue. Useful after fixing an issue on the destination side, or to re-send a notification that reached "Dead Letter".

• Run Dispatch Now: forces an immediate send without waiting for the next scheduled run.

What to do for each state?

A Failed state needs no action: the notification is retried automatically, with increasing delays. Only step in for notifications that reached Dead Letter: check the Last Error column, fix the cause (often the availability or address of the destination system), then use Requeue.

Frequently asked questions

Can the same item be received twice?
The system is designed to avoid duplicates thanks to a unique identifier per event. If a single item raises several distinct events, those are different notifications — which is normal.

Does the notification contain the full data?
No: it contains an identifier. The destination system uses it to retrieve the item afterwards. This keeps notifications light and fast.