Our dashboard says the batch is nearly done, but its counter includes repeat inspection attempts after a restart. We planned 209; we're doing sample verification on Universal Robots UR5e in a workshop batch inspection cell, using a small mounting plate. An item can fail and then have a reviewed retry.
I need unique accepted items counted while keeping the failed-check history
@NinaAdams0153 Pick a traceable item and compare all of its inspection attempts with its current accepted disposition. Does your counter count the attempts rather than the item?
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.
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.
@JamieChen1165 My own report showed attempt count separately from accepted-item count, making the reinspection history visible enough to explain why those totals differed.
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