our fr10 log reuses the job name after restart

Python has a sequence counter, but it starts over too. PLC trace includes the request change and receipt. Controller list only gives the repeated job name around that point

Does acknowledgement mean the inspection application received the request, or that the inspection result was available?

Owen, absolutely. Put any estimated clock offset in a separate comparison column. Do not edit the source time. If the evidence cannot distinguish the two attempts, the combined table should show that instead of choosing one for neatness.

Owen, originals kept untouched. HenryBaker, the authors confirm this acknowledgement is receipt only. It doesn't establish a result. We can align that request/receipt pair between Python and PLC before the restart

That gives you a useful piece of the sequence. Does anything identify the post-restart request independently of the reused label, or is that still where the reconstruction runs out?

That's where it runs out. Post-restart acknowledgement has no saved attempt identity beyond the recycled label. I can narrow its place in the PLC sequence, not say which application attempt owned it

Then don't squeeze an answer out of it. Can the next version carry an identity through restart, or will each source still be inventing its own label?

The authors need a common attempt reference and a defined lifetime for it. I would include source session and event meaning in the logging review too. Otherwise the next investigation could have unique numbers attached to three different definitions of accepted.

Will an unknown old acknowledgement stay unresolved when the updated application restarts?

That's in the change request. No plan to assign the old event using the new identity scheme; it can't recover information we never saved. Author is testing the new references through restart and duplicate receipt

Useful distinction. Has the incident summary stopped calling that receipt a completed inspection? That wording could mislead someone even with the timeline uncertainty clearly marked.