Capture And Recheck Record Versions

Context

Other people can change records while a bulk job waits or executes.

Decision and Origin

Interactive validation captures record versions for execution; keyed deliveries use producer-written versions under the reject policy, and conflicts can be validated as a new job. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Accept last-writer-wins updates by default: Unconditional writes can replace edits made after validation.

Retry a conflict using its old expected version: The stale version would conflict again; removing it changes the protection policy.

Consequences

Captured or supplied expected versions protect intervening edits; overwrite-policy deliveries without an expected version can replace them.

A record already containing the requested values can finish as applied and unchanged.

The console does not expose the keyed overwrite policy.