Call Workflow Service: "No FSConnection" error is thrown permanetly

Hi,

I wanted to bring this to the attention of the community as I am growing rather frustrated now. When manually deploying to the Knime Community Hub I extract the Executor ID and assigned, by editing the workflow on the Hub, the “executioContext”:

If I’d have not I’d get an error about the default executor conmtext not being assigned but we have only one and there is no option I can find that would make this the default.

ERROR Call Workflow Service 12:2384    Execute failed: 422 No execution context provided and space ''/Users/DataNautics Team/DataNautics Projects' (*211YLHCmdVG6Axhf)' does not have a default execution context assigned.

Now however, I am completely stuck as with Integrated Deployment to ease the manualy labor, this following issue has become so persistent that I cannot deploy / execute on the Community Hub et all:

ERROR Call Workflow Service 3:2384     Execute failed: Failure, workflow was not executed, current state is IDLE.
String to Path (Variable) 3:2:2379:0:2384:0:2381: Execute failed: No FSConnection was provided although FSLocationSpec indicates a CONNECTED_FS

I thought by switching to integrated deployment via Capture Workflow and Workflow Writer Nodes it would improve but quite the contrary. I wonder if I am too stupid. I checked all resources, rewatched the integrated deplyoment videos. Placed new Call Workflow Nodes in the version already on the Hub via remote editing. Nothing helps.

Anyone got an idea where or how I can resolve that?

PS: Here is the stack trace from the hub

2026-02-22 19:14:23,929 : ERROR : KNIME-Worker-2-String to Path (Variable) 3:1:2379:0:2384:0:2381 : [828de2ac-9ae7-483c-8ed2-25b4ca6ef757:02|efbea229-40d7-4b73-8b8e-eb3c391589b6] : Node                           : 3:1:2379:0:2384:0:2381 : Execute failed: No FSConnection was provided although FSLocationSpec indicates a CONNECTED_FS
java.lang.IllegalArgumentException: No FSConnection was provided although FSLocationSpec indicates a CONNECTED_FS
	at org.knime.filehandling.core.connections.location.FSPathProviderFactory.createConnectedFSPathProviderFactory(FSPathProviderFactory.java:137)
	at org.knime.filehandling.core.connections.location.FSPathProviderFactory.newFactory(FSPathProviderFactory.java:122)
	at org.knime.filehandling.core.connections.FSLocationFactory.<init>(FSLocationFactory.java:87)
	at org.knime.filehandling.core.defaultnodesettings.filesystemchooser.config.FileSystemConfiguration.createLocationFactory(FileSystemConfiguration.java:303)
	at org.knime.filehandling.core.defaultnodesettings.filesystemchooser.SettingsModelFileSystem.createFSLocationFactory(SettingsModelFileSystem.java:144)
	at org.knime.filehandling.utility.nodes.stringtopath.variable.StringToPathVariableNodeModel.execute(StringToPathVariableNodeModel.java:186)
	at org.knime.core.node.NodeModel.executeModel(NodeModel.java:605)
	at org.knime.core.node.Node.invokeFullyNodeModelExecute(Node.java:1331)
	at org.knime.core.node.Node.execute(Node.java:1038)
	at org.knime.core.node.workflow.NativeNodeContainer.performExecuteNode(NativeNodeContainer.java:618)
	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:143)
	at org.knime.core.util.ThreadPool$Worker.run(ThreadPool.java:277)

PPS: I noticed, thanks to the browser based inspection, that some nodes executed but it failed at a node which uses a a file system port that is provided by a shared component. I will rework this as that approach might be flaky.

PPPS: After reworking and trying to assign the executor ID I now got a Nullpointer Exception. What on earth is going on

ERROR Call Workflow Service 12:2384    Saving intermediate settings failed with NullPointerException
WARN  Call Workflow Service 12:2384    failed to apply settings: java.lang.NullPointerException: The parameter workflow-output-2390 does not exist in the properties.

I tested a few configuraiton changes to the Call Workflow Service Node and, once after removing the path to point to the workflow and set it manually, I was able to configure and execute without using a Path flow variable but manually setting the workflow. I reapplied the Path flow variable and it continue to work.

But then another NullPointerException accompanied by

ERROR Call Workflow Service 5:2384     Execute failed: No output with identifier workflow-output-2390

Removing the Path Flow Variable again resolved the NullPointerException. Here is the stack trace:

2026-02-22 21:32:15,822 : WARN  : main :  : WrappedNodeDialog : Call Workflow Service : 5:2384 : failed to apply settings: java.lang.NullPointerException: The parameter workflow-output-2390 does not exist in the properties.
org.knime.core.node.InvalidSettingsException: java.lang.NullPointerException: The parameter workflow-output-2390 does not exist in the properties.
	at org.knime.core.node.NodeDialogPane.internalSaveSettingsTo(NodeDialogPane.java:559)
	at org.knime.core.node.NodeDialogPane$4.run(NodeDialogPane.java:792)
	at org.knime.core.node.util.ViewUtils$3.run(ViewUtils.java:353)
	at org.knime.core.node.util.ViewUtils$2.run(ViewUtils.java:155)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.NullPointerException: The parameter workflow-output-2390 does not exist in the properties.
	at org.knime.core.node.util.CheckUtils.checkNotNull(CheckUtils.java:281)
	at org.knime.core.node.util.CheckUtils.checkNotNull(CheckUtils.java:208)
	at org.knime.workflowservices.knime.caller.WorkflowParameters.reorder(WorkflowParameters.java:271)
	at org.knime.workflowservices.knime.caller.WorkflowParameters.setOutputParameterOrder(WorkflowParameters.java:216)
	at org.knime.workflowservices.knime.caller2.CallWorkflow2NodeDialog.saveSettingsTo(CallWorkflow2NodeDialog.java:254)
	at org.knime.core.node.NodeDialogPane.internalSaveSettingsTo(NodeDialogPane.java:553)
	... 16 more

But then again another issue with Path Variable assignement.

Best
Mike