Workflow to Tool node failing on Hub - Tools that "have" workflow data area (data folder) are possible cause?

Hi all,

been trying to run some Agents on KNIME Pro / Team Plan and am encountering an issue in cases where everything works perfectly fine in KAP locally.

I experimented a fair bit with a minimal example to try and replicate…
Right now I am pinpointing the root cause to be tools that have a “data” folder (Files stored in Current Workflow Data Area)

so here we go:

Let’s start with something that works on Hub:

So now let’s change the tool and let’s write the data as .table file to workflow data area and also to data folder in tools folder (to be read relative to current workflow)
New tool - now reads from workflow data area:


Trying to run Agent in KAP whilst WFs are stored on HUB:

Extract from knime.log
Workflow to Tool #7: java.io.FileNotFoundException: File system element for parameter 'source' does not exist: 'C:\Users\marti\AppData\Local\Temp\knime_agent_10017\workflow_reader1312\data'
org.knime.core.node.KNIMEException: Errors in workflow - Contains one node with execution failure (Workflow to Tool #7)
	at org.knime.core.node.KNIMEException.of(KNIMEException.java:124)
	at java.base/java.util.Optional.map(Unknown Source)
	at org.knime.core.node.workflow.virtual.subnode.VirtualSubNodeOutputNodeModel.waitForContentToExecute(VirtualSubNodeOutputNodeModel.java:212)
	at org.knime.core.node.workflow.virtual.subnode.VirtualSubNodeOutputNodeModel.execute(VirtualSubNodeOutputNodeModel.java:172)
	at org.knime.core.node.NodeModel.executeModel(NodeModel.java:605)
	at org.knime.core.node.ExtendedScopeNodeModel.executeModel(ExtendedScopeNodeModel.java:86)
	at org.knime.core.node.workflow.virtual.subnode.VirtualSubNodeOutputNodeModel.executeModel(VirtualSubNodeOutputNodeModel.java:162)
	at org.knime.core.node.Node.invokeFullyNodeModelExecute(Node.java:1330)
	at org.knime.core.node.Node.execute(Node.java:1037)
	at org.knime.core.node.workflow.NativeNodeContainer.performExecuteNode(NativeNodeContainer.java:617)
	at org.knime.core.node.exec.LocalNodeExecutionJob.mainExecute(LocalNodeExecutionJob.java:98)
	at org.knime.core.node.workflow.NodeExecutionJob.internalRun(NodeExecutionJob.java:201)
	at org.knime.core.node.workflow.NodeExecutionJob.run(NodeExecutionJob.java:120)
	at org.knime.core.util.ThreadUtils$RunnableWithContextImpl.runWithContext(ThreadUtils.java:369)
	at org.knime.core.util.ThreadUtils$RunnableWithContext.run(ThreadUtils.java:223)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at org.knime.core.util.ThreadPool$MyFuture.run(ThreadPool.java:125)
	at org.knime.core.util.ThreadPool$Worker.run(ThreadPool.java:252)

Error when executing ad hoc job on Hub (KNIME Pro)


Log:
agenterrorlog.log (51.7 KB)

So now let’s change the tool back - delete the reader, insert table creator…

Now I’m getting similar error to when the reader was present…

Same if run as ad hoc execution on Hub:

So now the very interesting thing.

When I create a new tool from scratch and I place a CSV reader in it that reads a file available at a public URL…

Tool:

It works…
KAP with workflow on HUB:

Ad hoc execution:

Hello @MartinDDDD,

In 5.5.0 there is indeed a bug that breaks tools that are read from a “remote” path. Note that it’s about the path that is given to the Workflow to Tool node, the tools themselves can load remote data (as you have demonstrated with the CSV file). On an executor all paths are essentially remote, which is why this issue is most prevalent in this setting, however, it also occurs if you open the workflow from your hub space in your local AP.
The good news is that this will be fixed in 5.5.1 which will be released soon.

Best regards,
Adrian

2 Likes