Moving from KNIME v4.7.8 to KNIME v5.4.5, we are experiencing issues with the KNIME_BATCH_APPLICATION whenever a Credentials Configuration node is used in the workflow. The batch process just hangs indefinitely consuming 0% CPU, and the knime.exe task has to be killed manually. There are no errors logged to the workflow log file (attached). Any other configuration node, such as the String Configuration node, does not cause this issue. I’ve attached a very simple HelloWorld workflow with a Credentials Configuration node and a Send Email node to test this issue.
I still don’t have a solution, but I have come to a conclusion that the behavior of the Credentials Configuration node when running in batch mode (CLI) has changed.
The Credentials Configuration node has always been a UI component but it didn’t attempt to render the UI when running in batch mode and used the stored User ID and password in the node configuration.
In batch mode since KNIME AP v5, the Credentials Configuration node now renders the UI via a Command Prompt and ignores the values stored in the node configuration!!!
you might want to check the excellent article from