My UR5e sample-verification dashboard includes retries after restart in its nearly-done total. We planned 225 items, not 225 attempts. I need an accepted-item count while retaining failures and the reviewed retry history for each item.
Do the records preserve a stable item identity separately from the identity of each inspection attempt? Without that distinction you cannot reconstruct unique accepted items just by removing identical result rows.
Item labels are retained, but the dashboard increments on each successful attempt. Retry approval is in the history. I'll use that item relationship in the review rather than delete the failed attempts.
Define the acceptance decision per item with the person who owns verification, then derive the count from those decisions. Preserve every attempt, its result and the reviewed retry link. Test rebuilding after restart and replaying results without adding another accepted item; contradictory or unlinked records should remain visible for review rather than be merged by whichever result arrived last.
And does the proposed rebuild produce the same item decisions as the current session, including the fail-then-reviewed-pass example? That comparison would expose more than checking that the total never exceeds 225.