Table of Contents

Enum MessageFailureKind

Namespace
Excalibur.Dispatch
Assembly
Excalibur.Dispatch.Abstractions.dll

Classifies a message-processing failure to decide how the pipeline should react to it.

public enum MessageFailureKind
Extension Methods

Fields

Permanent = 1

A permanent failure that will not succeed on retry but is a property of the operation rather than the message itself — for example a validation, authorization, or programming error. Retrying is futile; the message is dead-lettered with the matching reason.

Poison = 2

A poison message that can never be processed because the message itself is defective — for example it cannot be deserialized, names an unknown type, or has no registered handler. Such a message is dead-lettered immediately, without consuming retry attempts, so it cannot block the pipeline.

Transient = 0

A transient failure that is expected to succeed on a later attempt — for example a network timeout, a temporary transport/database outage, or resource contention. The normal backoff retry policy applies.

Uncertain = 3

Delivery acceptance is unestablished: the operation may have taken effect. The default bounded retry policy permits replay, which requires idempotent consumers; this classification is not proof of rejection or non-delivery.

Unknown = 4

The failure is unrecognized; there is insufficient evidence that retry will recover. Do not automatically retry, acknowledge delivery or discard the message. Foreground callers receive the original failure; durable owners retain it for explicit classification and recovery. This is distinct from uncertain delivery acceptance.

Remarks

This is the single, shared failure taxonomy consumed by every resilience-aware component (retry middleware, retry policies, the outbox/inbox processors, and the change-data-capture processors) so that the decision "retry, or give up and dead-letter" is made consistently regardless of which component encountered the failure.

The classification is a value result, not an exception: classifying a failure is a common, expected operation on the hot path, so it never throws (cf. the predicate-outcome model used by resilience libraries such as Polly).