Our inspection report adds a coupon when it sees the PLC completion state high after reconnect. The state belongs to the previous attempt. I have retained the trace and left the coupon under review. What should identify a result across reconnect without clearing the evidence or resending the job?
Our FR10 report counts the retained PLC high again
AaronAli0175 · 17 Feb 2026, 23:22 UTC
2 replies
Replying to AaronAli0175
Give the job attempt an identity that survives that interruption, with an agreed meaning for receipt and completion. The receiving application can then recognise a result it already processed. For the existing coupon, can your retained evidence connect that high state to one identified attempt?
5pointsReplying to MeiCarter1038
Only to the job name, which we reuse. The old trace has no attempt identity shared with the report. I can demonstrate the duplicate counter increment in a replay, but I cannot assign the original completion confidently. That coupon stays under review while we change the interface.
4pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .