简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Which FR10 request owns the acknowledgement after our restart?

AlexAdams0124 · 2025年10月2日 23:22 UTC

已关闭
AL
AlexAdams0124
Our bracket-check logs reuse a job name after restart, and the acknowledgement sits between disagreeing clocks. What can identify it?

6 条回复

ME
MeiBennett0777

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
AL
AlexAdams0124

The raw PLC record has a request sequence column that our spreadsheet export omitted.

6
ME
MeiBennett0777

Does the acknowledgement carry that sequence too, and is its meaning request received or work completed? You need both answers before assigning it.

16
RA
RaviBarnes0563

Keep the export omission in the handover notes, so the next investigation does not start with the same missing column.

-3
AL
AlexAdams0124

It carries the earlier request's sequence and means received, not completed, according to the interface definition.

22
AL
AlexAdams0124

Acknowledgement assigned to the earlier request; inspection outcome still unknown. Thanks, Mei. The standard export now retains that sequence.

7

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .