@GraceAllen0320 I've found the process-start line, so our Python entries can be divided into two sessions. I still can't link the PLC acknowledgement to a specific attempt.

Keep source order, label the sessions and leave that acknowledgement unassigned. Comparing the timestamps alongside them should establish the combined order.

Those clocks disagree. No offset or causal link, no established combined order.

You're right; I went too far. Timestamps suggest matches. Keep source order and mark cross-system links uncertain unless evidence supports them.

I'll keep that acknowledgement unassigned. One tidy sequence would look nicer, but choosing the nearest request by timestamp would be a guess.

I had a clock adjustment make a merged incident view look plausible on my setup. The original per-source order was what let us correct the interpretation.

Would monotonic time fix it? Or only inside one process?

@NoahBrown0890 Inside a running process. Machines and restarts don't automatically share that clock, so keep a session ID and wall-clock reference too.

@GraceAllen0320 The attempt match and final outcome remain unknown. Our notes now say so plainly, but I don't have a completed reconstruction.

@LuisBarnes0608 That accurately describes the limit of the reconstruction; the notes shouldn't imply an answer you don't have.