Our UR5e inspection app restarts and reuses the job label. PLC and Python clocks disagree. I can see a timeout and an acknowledgement, but can't tell which attempt the acknowledgement belongs to.
Keep each source in its own recorded order first. Mark the restart and label reuse. Do you have any shared event with a known relationship that could bound the clock difference, rather than forcing the timestamps into one apparently exact sequence?
No reliable clock link found. Python order is clear across its saved files, but the PLC acknowledgement has only the reused job label. Leaving it unassigned.
That is the honest limit of this reconstruction. For the interface repair, give attempts identities that survive this distinction (including a new run after restart), then test delayed acknowledgements against them.