The command "conda init" is failing when executed using Automic Windows Command Action Pack
Article ID: 186722
CA Automic Workload Automation - Automation Engine
The command "conda init" is failing when executed using Automic Windows Command Action Pack. The error message in the report log is the following:
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If using 'conda activate' from a batch script, change your
invocation to 'CALL conda.bat activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>
Currently supported shells are:
See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.
The conda command has bug which prevents the command "conda init" from working properly.
Release : 12.x
Component : AUTOMATION ENGINE, CDA, Automic Windows Commands Action Pack
-As a first troubleshooting step, please execute the command "conda init" outside One Automation and see if that works.
-Please check if your conda version is the latest one