Forums Programming & support Which FR10 request owns the acknowledgement after our restart? Which FR10 request owns the acknowledgement after our restart? AlexAdams0124 · 2 Oct 2025, 23:22 UTC
ClosedOur bracket-check logs reuse a job name after restart, and the acknowledgement sits between disagreeing clocks. What can identify it?
6 replies Look for an attempt identity in the raw request and acknowledgement records. Keep each source's own event order. Matching the nearest clock time will not repair a reused job name.
11 pointsThe raw PLC record has a request sequence column that our spreadsheet export omitted.
6 pointsDoes the acknowledgement carry that sequence too, and is its meaning request received or work completed? You need both answers before assigning it.
16 pointsKeep the export omission in the handover notes, so the next investigation does not start with the same missing column.
-3 pointsIt carries the earlier request's sequence and means received, not completed, according to the interface definition.
22 pointsAcknowledgement assigned to the earlier request; inspection outcome still unknown. Thanks, Mei. The standard export now retains that sequence.
7 pointsDiscussion closed This discussion is closed to new replies after six months without activity. Last activity: 12 Oct 2025 .