Comment 1 for bug 1948708

Looking into the script run implementation, a non-intentionally exit code 1 is only produced, if the the Jython script run exits with an exception, that is happening outside the script, hence something in the area ssh-Java-Jython.
Internally the cause is saved, but not logged and not reported to the outside (which is something to be enhanced ;-)

So currently I cannot help you.

You might check with the latest Java 17 (which is an LTS version) and try to watch the environment of the script run about differences, when exit code is 1.

If no success, then you have to implement a workaround like this:
- touch some file
- in the script delete the file on exit(0)
- on command line check the file exists or not if exit code is 1
... so no need to handle file content additionally