Cannot assign the FR10 acknowledgement after our application restart
HassanBrown0878 · 22 Oct 2025, 11:52 UTC
21 replies
Does the acknowledgement carry anything besides that job label, Hassan?
11pointsHave you kept the original logs separately? I'd avoid adjusting all their times in the only copies.
10pointsBuild 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.
15pointsGabriel, label only in the application display. Sam, original files are untouched.
9pointsLook 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.
14pointsGrace, would you use connection loss as a common event, or is that too loose?
16pointsIt 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.
18pointsThat's helpful, Grace. I was about to use the two disconnect entries as though they were simultaneous.
16pointsThe raw reply has a sequence field. Our display hides it. Thank you, Anil.
13pointsNow 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.
24pointsHassan, does the saved request include that field too?
22pointsYes. Different values on the two sends.
18pointsIf 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.
6pointsAnil, would you still compare the controller events once a request match is found?
9pointsYes, 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.
12pointsProtocol says request received, with its sequence echoed. It matches the earlier send.
15pointsSo is the newer attempt still unanswered, Hassan?
25pointsFor 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.
6pointsNewer receipt unknown, Gabriel. Neither inspection outcome is established from this reply.
23pointsDid the application treat that earlier receipt as success for the newer attempt, or only display it?
14pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .