Why did restarting our FR5 check give two attempts the same name?

JackBrooks0863 · 23 Oct 2025, 06:31 UTC

Closed
JA
JackBrooks0863
I have one coupon in the review tray and two entries called CHECK-8, which is not making our handover any easier. The first request timed out, somebody restarted the application, and the next request got the same label. There is one acknowledgement in the controller export. Our developer thinks its time puts it against the second request, but the laptop and PLC clocks disagree and nobody measured the difference during the incident. Can we actually assign this result, or are we trying to make a tidy answer out of a name we should never have reused?

6 replies

BR
BrunoChen1148
Replying to JackBrooks0863

You cannot choose between those attempts from the label. And someone still has to decide what happens to the coupon while the software argument continues.

11 points
NA
NaomiBarnes0593
Replying to JackBrooks0863

Was there a separate inspection result, or only acknowledgement of the request? Those are different events in our acceptance checks.

8 points
JA
JackBrooks0863
Replying to NaomiBarnes0593

Only the acknowledgement, Naomi. Quality has the coupon and hasn't accepted it. Bruno, the handover now says that explicitly; I'd assumed the review tray was enough of a hint, apparently not.

21 points
BR
BrunoChen1148
Replying to JackBrooks0863

The tray tells your shift. The report may travel further. I would leave both attempts visible and the acknowledgement unassigned unless another identifier turns up.

8 points
JA
JackBrooks0863
Replying to NaomiBarnes0593

There isn't another identifier in the export. Thanks for the distinction, Naomi, I was calling it a result too. We're changing the restart naming, but that won't tell us which old request this acknowledged.

14 points
NA
NaomiBarnes0593
Replying to JackBrooks0863

Did quality finish the separate coupon decision? The unassigned acknowledgement should not leave that physical item waiting indefinitely.

12 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .