127 brackets cannot be reconciled from a total of inspection attempts

ReeceCarter0993 · 30 Jul 2026, 15:22 UTC

Reply to discussion
RE
ReeceCarter0993
I need the accepted count for our 127-bracket UR5e batch to represent physical items, but the restarted dashboard counts repeated inspections; how should I keep failed checks and reviewed retries without letting them become extra accepted brackets?

15 replies

PR
PriyaArcher0394
Replying to ReeceCarter0993

Our shift needs to see the bracket's disposition separately from the number of times it was checked; does the same physical bracket retain a stable label through retry?

22 points
RE
ReeceCarter0993
Replying to PriyaArcher0394

Yes, labels are stable within the batch; completed attempts currently drive the counter whether or not they add a newly accepted bracket.

19 points
LI
LinBrown0879
Replying to ReeceCarter0993

Build the total from distinct accepted batch-item records. Keep attempts attached; don't edit history to fit the desired number.

7 points
MI
MiaBennett0731
Replying to LinBrown0879

First settle what accepted means after a reviewed retry or a later failure. Otherwise distinct labels alone can still produce the wrong total, just without obvious duplicates.

8 points
AN
AnnaBell0677
Replying to MiaBennett0731

Who is authorised to change that disposition, and who sees items still awaiting review?

6 points
RE
ReeceCarter0993
Replying to AnnaBell0677

Quality owns disposition; I'm asking for the written rule and keeping pending items visible rather than counting them as finished.

14 points
PR
PriyaArcher0394
Replying to ReeceCarter0993

Keep the attempt that led to that disposition identifiable too, so an operator can find the actual accepted check rather than browse every retry

9 points
LI
LinBrown0879
Replying to PriyaArcher0394

And preserve the other attempts. A link to the accepted one isn't a reason to discard the failures.

21 points
MI
MiaBennett0731
Replying to LinBrown0879

For software tests, replay the same events twice and reconstruct after restart. Both routes should reach the same per-item dispositions and total under quality's rule, not merely stop the screen adding twice.

25 points
RE
ReeceCarter0993
Replying to MiaBennett0731

Quality has agreed the rule, including the review hold after a later failure; the revised report derives totals from item disposition and links every attempt beneath its bracket.

23 points
AN
AnnaBell0677
Replying to ReeceCarter0993

Can the supervisor distinguish remaining unaccepted brackets from missing inspection records? Those are different work queues.

7 points
RE
ReeceCarter0993
Replying to AnnaBell0677

Yes, the report separates those states and shows uncertain records explicitly; thank you Anna, our old nearly-done display hid that distinction.

8 points
LI
LinBrown0879
Replying to ReeceCarter0993

Have you checked the corrected batch against the retained inspection and review records, not just against itself after restart?

5 points
RE
ReeceCarter0993
Replying to LinBrown0879

Quality reconciled this batch against those records, and duplicate replay plus restart reconstruction preserve the same accepted total; the attempt history remains intact, so we have released the corrected report.

12 points
MI
MiaBennett0731
Replying to ReeceCarter0993

Keep that reconciled example with the tests. It gives the next maintainer an expected item-level answer, not merely a plausible-looking grand total.

8 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.