Requester notice delivery

The Lifecycle

Transitions Explained

Delivery first claims a job-and-outcome row, then resolves the requester, sends or suppresses the message, and records the result. Delivered and suppressed outcomes stop later claims. Pending and failed outcomes can be claimed again if another delivery invocation occurs.

What Cannot Happen

A delivery exception does not propagate to the job. Claim refusal protects ordinary sequential replay, but the outcome updater itself does not protect terminal notice states. Another sender can overwrite a result using the same row identity.

Concurrency and Timing

The protocol allows two claimants to send and leaves an interruption window between send and outcome persistence. No independent retry sweep guarantees that failed or abandoned notices receive another invocation.