I'm reconciling our batch of 162 for per-item inspection with Fairino FR10 in a fixture inspection station with item labels, using an inspection coupon.
The dashboard looks nearly finished because its post-restart counter includes repeat inspections.
Items can have failed checks followed by reviewed retries.
I want the accepted-item count to be accurate without discarding that attempt history.
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?
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.
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.