Our FR10 log reuses a housing job label after restart. Which attempt owns the delayed acknowledgement?
Does the acknowledgement carry anything besides that job label, Hassan?
11分简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
Cannot assign the FR10 acknowledgement after our application restart
HassanBrown0878 · 2025年10月22日 11:52 UTC
21 条回复
Have you kept the original logs separately? I'd avoid adjusting all their times in the only copies.
10分Build the attempt sequence within each source first. You can then look for shared events or identifiers to relate them, without assuming the wall clocks were aligned.
15分Gabriel, label only in the application display. Sam, original files are untouched.
9分Look at what the receiver actually returned, not just the display. On another interface discussion the important question was what the receiver retained, and a friendly label on the slide did not answer it.
14分Grace, would you use connection loss as a common event, or is that too loose?
16分It can bound part of the sequence, but different components may detect the loss at different times. I would not align their clocks on that event alone, especially when a timeout is involved.
18分That's helpful, Grace. I was about to use the two disconnect entries as though they were simultaneous.
16分The raw reply has a sequence field. Our display hides it. Thank you, Anil.
13分Now check what the request carried and whether that sequence can repeat after restart. Finding another number is useful; it isn't the match until its meaning is clear.
24分Hassan, does the saved request include that field too?
22分Yes. Different values on the two sends.
18分If the protocol defines the returned field as the request sequence, compare those saved values directly. Keep the protocol meaning with the report, since an unrelated internal counter could look equally convincing.
6分Anil, would you still compare the controller events once a request match is found?
9分Yes, Sam, for what the controller was doing. A matched acknowledgement may only say the request arrived. Don't turn it into a completed inspection unless that is what the interface says it means.
12分Protocol says request received, with its sequence echoed. It matches the earlier send.
15分So is the newer attempt still unanswered, Hassan?
25分For the handover, keep the earlier receipt beside the earlier request and show the later attempt separately. Any eventual inspection result needs its own interpretation; the receipt should not fill that blank.
6分Newer receipt unknown, Gabriel. Neither inspection outcome is established from this reply.
23分Did the application treat that earlier receipt as success for the newer attempt, or only display it?
14分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .