Enum ProjectionHaltReason
- Namespace
- Excalibur.EventSourcing
- Assembly
- Excalibur.EventSourcing.Abstractions.dll
What caused processing to halt, so a caller can tell a transient stop from a terminal one.
public enum ProjectionHaltReason
Fields
CheckpointWriteFailed = 4The projection applied cleanly but its checkpoint could not be recorded, so the work is not durably acknowledged. Not necessarily permanent, but never a success: the page is redelivered.
EventUndeserializable = 2An event in the page could not be deserialized into a domain event. Terminal: it will not deserialize on a later attempt, so the page is held rather than skipped and the event needs attention.
None = 0The invocation did not halt. The only valid value for a non-halted outcome.
The next contiguous prefix of the stream could not be read yet, which is the normal reading of an append still in flight. TRANSIENT: it clears without intervention, so waiting is the correct response.
ProjectionFaulted = 3A projection's apply threw, or its write could not be confirmed. Terminal for that projection: waiting does not resolve it, and treating an unconfirmed write as applied is precisely the silent loss this seam refuses.
SubscriptionMembersNotHosted = 5The subscription's roster holds projection members this process does not host, so this process cannot establish that the subscription reached the stream head. Terminal here: which events an absent member consumes is not recorded anywhere, so waiting does not resolve it -- that member advances only in the deployment that hosts it. Drive the processor there, or host every member bound to the subscription in one deployment.
Remarks
Halted alone is not actionable. It is produced for causes with opposite correct responses: a prefix that is merely not readable yet clears on its own and should be waited for, while a faulted projection, a poison event, or an unconfirmed write do not clear by waiting and must never be reported to a caller as success.
This matters most on the inline save path, where the caller's events are ALREADY COMMITTED. Retrying a transient halt there turns a needless "your durable write is pending" into a correct success; retrying a terminal one turns an unconfirmed write into a reported success, which is the silent failure class the positioned projection design exists to prevent. Only PrefixUnavailable is safe to retry.