Issue with "Call Workflow Service" Node in Scheduled Task

KNIME Server
1

Team,

We are encountering an issue with the “Call Workflow Service” node. When running the node manually, it successfully calls the subflow as expected. However, when it’s triggered via a scheduled task on Windows, it throws an error stating it couldn’t find the respective mount point.

We attempted to resolve this by using the “KNIME Mountpoint Connector” node, but we still couldn’t establish the connection. The “KNIME Server Connector” node isn’t feasible for us, as it prompts for a password. We use a vault password, which we cannot manually enter.

Any assistance or guidance on this would be greatly appreciated.

2

@vamsi4uonly there is a reason for the existence of KNIME Business Hub and Community Hub.

Having said that: I assume it might have to do with relative paths and batch execution. I have found that relative paths, also KNIME paths like knime:// … do not work well in batch mode. One idea could be to provide the absolute path via workflow variables in the batch file. More details: