Merge Attempt And Its Job

The Lifecycle

Transitions Explained

Submission commits a queued attempt and its job. The executor’s running claim belongs to the business transaction, so ordinary readers need not see it while locks are held. Success commits the attempt and outcome; rollback restores queued standing until failure settlement commits.

What Cannot Happen

A successful attempt cannot be failed later or reversed. A new execution after failure creates a separate attempt, and overlapping merges cannot both absorb one participant.

Concurrency and Timing

Job reporting begins before the business transaction and settles its four steps afterward. Lock waits are capped at five seconds; a caught lock timeout normally becomes a failed attempt and task refusal. Workflow retry applies to transient task errors that escape that settlement, within the fifteen-minute task and twenty-one-minute workflow limits.