Our FR5 bracket acceptance logs show a timeout. Python, PLC and controller clocks disagree, and the job label repeats after restart. I cannot tell which attempt owns the acknowledgement.
Preserve each original log and its internal event order, then separate sessions using actual restart evidence; a reused label and nearby timestamp are not enough to join an acknowledgement to an attempt. Ask the interface owners what independent correlation evidence they retain.
Restart identified in two logs. Interface owners found no independent attempt identity in the retained acknowledgement. Both associations remain possible; I have marked it unassigned.
Then leave that outcome unresolved and keep the affected bracket in the agreed reconciliation process; future restart-safe identifiers can prevent this ambiguity, but cannot reconstruct evidence the old records never retained.