Background work follows the queued-work standard, delivered at least once

Context

Durable work does not remove duplication at external boundaries.

Decision

Run queued executions, received-message processing, event routing and subscription delivery through durable queue records, dispatchers and workers. Recipients must tolerate repeated transport attempts.

Alternatives Considered

Guarantee exactly-once transport with a distributed transaction. Providers and consuming applications do not share the database commit boundary.

Call consumers inside the source mutation. Slow external work would hold the writer and a crash could lose dispatch.

Consequences

Adapters and consumers deduplicate the identifiers supplied by their envelopes.

Exhausted work remains inspectable and supports authorized recovery.

A routing retry may revisit a consumer that already completed the prior attempt.