Why does reconnect give our UR5e coupon another finished tick?

Recipe number and a local counter. The counter resets when the job is reopened, so its value appears in two runs. No shared run identifier in the export.

Does the duplicate exist in the saved report too, or only on the screen?

Replay the retained state offline. Keep the original history present, not an empty test database.

Our shift once corrected a display total while leaving the exported report unchanged. The next planner reasonably trusted the file. I'd check both paths before describing this as a colour or counter problem.

Both paths, Anika. Aisha's point applies: the extra row is saved, not just drawn. Developer has a replay with the existing history; the original retained state remains unassigned to either run.

Keep that uncertainty after restart too. Otherwise the next launch forgets why it was held.

And repeat the same delivery. One successful reconnect test may still hide duplicate counting.

Who reviews the physical coupon while the software history stays uncertain?

Mark, if quality can decide the physical coupon, link that reviewed decision without inventing a missing software sequence. We needed both the practical disposition and an honest explanation of why the old report changed.

Quality owns that review. The proposed correction links its decision to the coupon and incident, leaving the unknown old attempt unassigned. I'm not treating the eventual physical decision as a recovered log.

Has the replay stopped another row appearing in the exported report?

In the developer's replay, yes. Repeated delivery stays one recorded event. Restart with the held reason retained is the next test, so not a completed fix yet.

Include a genuinely different completion too. Rejecting everything would look impressively duplicate-free.

And show the held reason to whoever covers the next shift.

Liam's new-event case matters to the operator explanation as well. People need to distinguish waiting work, completed work and an old uncertain event without assuming every warning means they should repeat the inspection.

New completion and retained-hold restart cases are added. Quality has released the coupon under the review process. Thanks Aisha, that kept the physical decision moving without pretending we found the missing run identity.

Who approves the final report adjustment when those software checks are finished?