I've got two inspection attempts called 'housing-test' on our FR10 bench. The application restarted between them. Python, PLC and controller clocks disagree, so putting the entries in time order makes a very tidy story I don't trust. Is there another way to join them up?
Start with something the systems recorded in common, such as an attempt identifier or a distinctive request sequence, and keep the two runs separate while you compare; does the original trace contain either?
There is a restart boundary in Python, but nothing unique carried into the PLC trace for either request. The developer could only narrow the acknowledgement to those two attempts, not choose one. I've left it unassigned. Irritating, but better than decorating a guess with a timestamp.