I've traced one item in our saved history and found several successful attempts with the same identity. Our counter adds each success, inflating the apparent batch progress.

Rebuild an offline total from item dispositions, keeping attempts underneath. Counting each accepted identity once should give you the right batch total.

Your counting rule needs the current disposition. Deduplicating all identities with any successful attempt would still include an item whose disposition was subsequently changed to rejected.

@ReeceChen1167 Right. I should've said current authorized disposition. Keep the full history, but count an item only if its current disposition makes it accepted for this batch.

For an item that fails and then gains reviewed acceptance, should the report count one accepted item while preserving both inspection attempts beneath it?

@JamieAli0208 Yes. Attempts explain its history; current disposition determines whether that item contributes to accepted quantity.

On my report, we put attempts and accepted items beside each other. People stopped expecting the numbers to match once the repeated inspections were visible.

@ZaraBarnes0569 Does a retry get a new item ID then? Or just a new attempt ID?

Same physical item, same item identity. The distinct inspection gets its own attempt identity, linked back to that item.

The newer entries distinguish item and attempt identity, but some older results lack the item link needed to include them reliably in an accepted-item total.

@JamieAli0208 Avoid inferring unique items solely from event order; those unidentified results might contain repeated attempts against the same physical item.

@ReeceChen1167 The report's counting basis is clear: use current accepted dispositions per item, preserving all attempts. Completing the fix still depends on traceable reconciliation and a consistent offline restart result.

@JamieAli0208 That rule preserves the inspection history and gives the total a clear basis, with reconciliation still required for closure.