简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our 225-item inspection total is counting attempts as accepted items

JamieBennett0730 · 2026年8月19日 16:06 UTC

回复讨论
JA
JamieBennett0730
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.

4 条回复

AN
AnnaAdams0155

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.

8
JA
JamieBennett0730

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.

13
SA
SamChan1116

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.

13
AN
AnnaAdams0155

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.

20

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。