Table of Contents

Enum CloudAppendOutcome

Namespace
Excalibur.Data.CloudNative
Assembly
Excalibur.Data.Abstractions.dll

What a cloud-native append actually did, as a single named outcome rather than a combination of flags.

public enum CloudAppendOutcome

Fields

AlreadyCommitted = 1

The events were already durably present when this call ran, and the store recognised them as its own by identity rather than writing them a second time.

This is a success — the append is durable — but it is distinct from Committed: the rows were written by an earlier call whose acknowledgement was lost, and present does not imply retrievable. A caller still holding the live payloads must not assume they are what the store would now return.

Committed = 0

This call wrote the events and the store acknowledged the write.

ConcurrencyConflict = 2

The append lost its version precondition to another writer. Nothing was written.

Failed = 3

The append failed for its own reasons. Nothing was written.

Unknown = 4

The provider cannot determine whether the complete atomic append committed.

This is neither success nor proof of rollback. Reconcile using the original operation identity.

Remarks

The provider-neutral twin of this enumeration lives beside the event-sourcing append result. It is restated here rather than shared because the dependency runs the other way — the event-sourcing abstractions reference this assembly, not the reverse — and this small value type is cheaper to restate than a namespace every consumer of the core append result would have to import.