Skip to content
English

DeadLetter

Defined in: src/SystemMessages.ts:165

Wraps an undeliverable message sent to dead letters.

new DeadLetter(message, sender, recipient, attribution?): DeadLetter

Defined in: src/SystemMessages.ts:166

unknown

ActorRef<unknown> | null

ActorRef

DeadLetterAttribution = NO_ATTRIBUTION

What the envelope was carrying beyond its payload, where the loss path still had the envelope to copy it from (#773).

Empty everywhere else, and that is honest rather than lazy: a letter built from a bare message — a projection event, a singleton hand-off, a Terminated with no provenance — never had an MDC snapshot or a span context to lose, so an absent field says “there was none”, not “we did not bother”.

DeadLetter

readonly attribution: DeadLetterAttribution = NO_ATTRIBUTION

Defined in: src/SystemMessages.ts:180

What the envelope was carrying beyond its payload, where the loss path still had the envelope to copy it from (#773).

Empty everywhere else, and that is honest rather than lazy: a letter built from a bare message — a projection event, a singleton hand-off, a Terminated with no provenance — never had an MDC snapshot or a span context to lose, so an absent field says “there was none”, not “we did not bother”.


readonly message: unknown

Defined in: src/SystemMessages.ts:167


readonly recipient: ActorRef

Defined in: src/SystemMessages.ts:169


readonly sender: ActorRef<unknown> | null

Defined in: src/SystemMessages.ts:168

toString(): string

Defined in: src/SystemMessages.ts:192

Deliberately unchanged by the attribution (#773).

The MDC routinely carries tenant, user and request identifiers, and this string is what an operator pastes into an issue. DeadLetterRef already keeps the payload out of its log line for exactly that reason, and a toString that printed the context would put the same class of data back into the same place through a different door. Anything that wants the attribution reads the field.

string