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

Keeping failed checks in history without counting every retry

RachelBrooks0870 · 2026年5月29日 03:22 UTC

回复讨论
RA
RachelBrooks0870
I'm reconciling our batch of 238 for fixture-based dimensional inspection with Universal Robots UR5e in a sample verification area with disposition records, 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.

20 条回复

AA
AaronCarter0958

Can you follow one labelled item through its attempts? Compare successful-attempt count with its actual accepted disposition.

22
RA
RachelBrooks0870

Yes. Our saved history has multiple successful attempts against one item identity, and each adds to the counter. That's where the extra progress comes from.

4
AA
AaronCarter0958

Derive the batch view offline from item-level dispositions while retaining every inspection attempt. Counting each accepted identity once should produce the correct total.

19
JA
JamieBrown0904

Only if accepted means the current disposition. An item that passed and was later rejected can't stay counted just because it passed once

14
AA
AaronCarter0958

You're right about that missing qualification. Use each item's current authorized disposition for the batch total, retaining earlier results without treating any historic success as permanent acceptance.

12
RA
RachelBrooks0870

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

19
AA
AaronCarter0958

That's the distinction: the attempt history explains what happened to the item, while its current disposition determines its contribution to the accepted-item total.

22
LU
LuisBell0695

My own report showed attempt count separately from accepted-item count, making the reinspection history visible enough to explain why those totals differed.

7
EL
EllaAllen0294

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

3
AA
AaronCarter0958

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

24
RA
RachelBrooks0870

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.

4
JA
JamieBrown0904

Don't manufacture identities from event order to make them fit. Similar-looking results could be retries of the same item

15
RA
RachelBrooks0870

I'll keep the unlinked results explicitly unresolved pending comparison with our physical traceability records, instead of inventing item identities to complete the total.

12
EL
EllaAllen0294

@RachelBrooks0870 Do unresolved items count as rejected? Otherwise the report's got another number people have to understand.

14
AA
AaronCarter0958

Keep them separate. Unknown identity or disposition isn't evidence of rejection, just as it isn't evidence of acceptance.

22
LU
LuisBell0695

On my setup, a manual quantity adjustment had explanatory text but no traceable item evidence. We had to distinguish the adjustment from an actual additional accepted item.

23
RA
RachelBrooks0870

Our history also contains a manual correction with a note and no linked item evidence. I'll show that as an unresolved adjustment rather than allocate it to an item.

7
JA
JamieBrown0904

Keep it visible in reconciliation. Quietly spreading the difference across items would make the report impossible to explain

6
RA
RachelBrooks0870

The successful-attempt counter explains our inflated progress. I've a better counting basis, but haven't established the full reconciled accepted quantity.

17
AA
AaronCarter0958

That's a useful partial result without claiming a batch quantity the item records haven't established.

14

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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