Data Job Batch

The Lifecycle

Transitions Explained

Every planned batch begins pending. Delivery records an attempt before item processing; conditional completion makes finished progress resistant to duplicate deliveries. Exhausted transient work waits for operator recovery, while abandoned work has a separate not-attempted state. Approval and dependency retry can reopen completed batches.

What Cannot Happen

A finished delivery does not reopen itself. Explicit recovery determines which batches become pending again.

Concurrency and Timing

Receipts protect concurrent delivery, while queue claims reduce ordinary duplication. CRM retries through transport; Platform retries immediately in process and can lose claimed work if the request stops.