Our housing check timed out, the application restarted under the same job name, and now someone wants to attach a late acknowledgement to the newer attempt because its timestamp is closer; with Python, PLC and controller clocks disagreeing, what actually links it?
Replying to MinaBrown0946
Look for an identity shared by the request and acknowledgement, plus source-session information; keep each log's local order intact, but if the only common detail is that reused job name, say the ownership is unresolved rather than choosing the nearest clock reading.
10 points