I have two maintenance laptops on the bench. Our FR10 status script works on the older one. The rebuilt one complains about an unexpected argument before any connection attempt.
The job files have been checked. The Python environment has not. There are three SDK directories on the rebuilt machine and the shortcut points at a fourth folder containing our scripts. I need to identify what it actually imports before the next person spends another shift reinstalling things.
I once chased a missing package that existed perfectly happily in the wrong interpreter. Half an afternoon to discover we'd been having two different conversations with Python.
The icon loads the same local SDK copy after all. Different interpreter, same imported file. The callable in that copy takes different arguments from the one on the working laptop.
Our controls engineer owns it. She found the version note in her old handover email. That agrees with the working laptop, including the argument used here.
We rebuilt the intended environment and moved the stray SDK copy out of the script directory. Both launch routes now report the agreed paths and the read-only status check works. The shortcut details are finally in the handover.