The rebuilt shortcut imports from an old training folder. The working laptop imports from the maintenance folder. Finally something we can actually compare.

Note the Python executable as well. A replacement shortcut that only changes the folder can still leave the next person using a different environment.

Does the argument list in the imported training copy match the maintenance copy? That will tell your maintainer whether this error follows the local interface difference before considering any controller-side explanation.

Yasmin, did the maintainer find that difference?

Yes. The training copy has a different call signature. The maintainer compared the actual imported files, not the folder dates, and reproduced the argument failure without a controller connection. We have selected the working environment for this script and are fixing the normal shortcut to use it.

Run it from the handed-over shortcut after a fresh sign-in. That's what the person covering you will use, not the terminal where the maintainer has everything set up.

And retain the selected SDK identity alongside that executable path. Identical directory names are doing rather more work here than they deserve.

Fresh sign-in, normal shortcut, expected imported copy. The read-only query now returns the fixture identity we expected. Nothing changed on the controller. Thank you, Will, that first path check saved us a pointless round of hardware explanations.

Good to hear. The shortcut check makes that a usable handover.