# Expected Diagnosis: batch-update-row-processing-anomaly

The expected result should converge on the case-specific mechanism below while
keeping conclusions bounded by the collected evidence.

## Expected conclusion

Two compensation batch-update jobs overlapped in both schedule and ID range. A commit-time write conflict forced retry after log_status had changed, causing the retried statement to scan a broad index range and perform a large table lookup before filtering. The fix is to remove overlap, extend the interval, reduce batch LIMIT and concurrency, rather than applying resource binding.

## Required evidence chain

- Show that the anomalous task overlaps another compensation job in time and key range.
- Identify the commit-time write conflict and retry as the transition into the expensive path.
- Explain how the changed status value causes broad index lookup followed by filtering, producing large Selection actRows.
- Recommend removing overlap, increasing the schedule interval, and reducing batch size or concurrency; resource binding does not remove the contention mechanism.