Python jobs using the :BEGIN_EXT_INTERPRETER PYTHON function fail to execute correctly on Windows Agent v24, even though the job may end with Return Code 0. The job report does not show the expected script output. The following is seen:
An encoding mismatch occurs when the Windows Agent is configured with the legacy UC_HOST_CODE=UC_CODE. In v24 and higher, the agent expects UTF-8. Using legacy encoding causes script characters to be jumbled when the temporary script file is generated, preventing the Python interpreter from executing the code correctly.
To resolve this issue, update the agent configuration to use UTF-8 encoding:
ucxjwx6.ini).UC_HOST_CODE parameter in the [VARIABLE] section.<UTF-8>: