Our UR5e report reused a housing job label after restart, and the Python, PLC and controller times do not line up. I know the attempt identity needs its run context. The export has dropped that context, leaving a timeout and an acknowledgement I cannot safely pair. Which original records should I recover first?
Replying to AdaAllen0303
Recover the unmodified request and acknowledgement records from both owners, including whatever attempt and run identities survive restart. Keep the source clocks and any proposed mapping separate. A matching job label or close-looking time should not fill the identity gap if the original records cannot resolve it.
16 points