Dead letters
Weik.io 2026.2A failed event lands in the dead letters. Once you have fixed the cause, send it to its reader again with weikio deadletters resend. Product page · Video
Watch: Dead letters, 3:23
The video follows a failed event into the dead letters and sends it to its reader again with weikio deadletters resend.
This part of the video couldn't be loaded.
On this page
When an event still fails after its last attempt, Weik.io copies it into the environment’s dead letters and records the integration it failed in and the reason. The dead letter stays there until you send it again or discard it. The channel’s other readers carry on with their events.
See the dead letters#
$ weikio deadletters list --env productionFor each dead letter, the list shows:
- The position
- The time
- The reader it failed in
- The channel, transfer, schedule or entity type it came from
- The number of deliveries it had
- The reason
You can narrow the list to one channel or one reader:
$ weikio deadletters list finance/invoice-created --env production --since 24h
$ weikio deadletters list --env production --integration finance/invoice-archiverweikio deadletters show --seq 1043 --env production prints one dead letter in full, including the event’s headers and body.
In the admin UI, Events › Dead letters lists the same dead letters with their headers and bodies. From there you can send one or a selection again, or discard them.




Send them again#
Fix the cause first, such as the upstream that was down or the bug in the route, and deploy the fixed version. Then send the dead letters again:
$ weikio deadletters resend --seq 1043 --env production
$ weikio deadletters resend finance/invoice-created --env production --since 24hEach dead letter goes only to the integration it failed in. The CLI prints how many it sends and sends them once you confirm. To skip the question, pass -y.
A resend fails and keeps the dead letter when its integration can’t receive the event now, for example because it was undeployed. It also fails when Weik.io no longer keeps the event, because the dead letter doesn’t have the body.
Discard them#
Discard a dead letter you don’t need, such as an event the reader should never have had or one you handled by hand:
$ weikio deadletters discard --seq 1043 --env productionHow long they stay#
An environment keeps its dead letters for 30 days by default. When you delete an integration, its dead letters stay. To reach them, pass the integration’s ID to the weikio deadletters commands with --record-id.
Skip ahead or rewind a reader#
When a reader is far behind, or you want it to read a part of the channel again, move the reader:
$ weikio reader skip finance/invoice-archiver --channel invoice-created --env production
$ weikio reader rewind finance/invoice-archiver --channel invoice-created --to-seq 48000 --env productionskip passes over every event the reader hasn’t finished, so it gets only what is published from now on. rewind delivers the events again from the position you give. Both print how many events they pass over or deliver again before they do it.
In the admin UI, the integration’s Event delivery section has the same actions as Skip to now and Rewind. It also shows each reader’s figures, such as how far behind it is and the age of its oldest event.
Send any stored event again#
You can resend any event Weik.io still keeps, to every reader or to one:
$ weikio events resend finance/invoice-created --env production --seq 48213 -yTarget: https://hub.example, project finance (argument), environment production (--env)
event 48213 resent as 48397 (Weikio-Resend-Of: 48213)--to finance/invoice-archiver sends it only to that integration. The event keeps its ID, so a route that handles each event once with #weikioIdempotent skips one it already handled.