Container Input (JSON): default parameter name not working ("json-input")

[Mol1hua]

Hi there,

We are trying to call a workflow using the Knime REST API on our Knime server.
The workflow contains one Container Input (JSON) node with node id 3819.
The setting “Append unique id to parameter name” is unchecked.

The json we sent via REST call contains the default wrapper “json-input” (as also mentioned in #13461 .
However, the workflow is expecting “json-input-3819” and the REST call fails with http error code 500.

11-Jan-2022 10:02:13.937 SEVERE [http-nio-8080-exec-16] com.knime.enterprise.server.rest.impl.providers.exception.ExecutorExceptionMapper.toResponse Could not set input on job 'd6fbe740-5404-458b-9103-ac2db881aac0': 
Parameter name "json-input" doesn't match any node in the workflow, valid parameter names are: ["json-input-3819", "json-input-0:3896:3935", "json-input-4033:3974:3841", "json-input-4033:3974:3973:3824", 
"json-input-4033:3974:3989:3841", "json-input-4038:3935", "stationnumber", "processlayer", "json-input-4049:3974:3841", "json-input-4049:3974:3973:3824", "json-input-4049:3974:3989:3841"]
         com.knime.enterprise.utility.ExecutorException: Could not set input on job 'd6fbe740-5404-458b-9103-ac2db881aac0': Parameter name "json-input" doesn't match any node in the workflow, 
         valid parameter names are: ["json-input-3819", "json-input-0:3896:3935", "json-input-4033:3974:3841", "json-input-4033:3974:3973:3824", "json-input-4033:3974:3989:3841", "json-input-4038:3935", 
         "stationnumber", "processlayer", "json-input-4049:3974:3841", "json-input-4049:3974:3973:3824", "json-input-4049:3974:3989:3841"] 

How can we call the workflow via REST without specifying the node id of the container?
Any help would be greatly appreciated.

[Mol1hua]

KNIME Server version: 4.13.4
KNIME version 4.4.2

[julian.bunzel]

Hey @Mol1hua,

Hope you are doing well!
Are you sure that there really is only one Container Input node in the workflow?
Usually, the node id is only necessary in case that there are multiple Container Input nodes that have the same parameter name. You could also try to rename the parameter name of your Container Input to avoid having duplicate parameter names.

I double checked it on my test server and this issue only occurred when I added a second Container Input with the same parameter name.

Best regards,
Julian

[Mol1hua]

Hi @julian.bunzel

thank you for your reply!
That was a great tip!
We downloaded the workflow to a local computer and searched the directory for the node name.
We actually had nested components which also used container input (json) nodes.
These were not needed and we replaced them with table creator nodes.
Now the error no longer occurs!

I really appreciate your support.

[julian.bunzel]

Hi @Mol1hua,

Thank you!
Great to hear that it’s working now.

Best regards,
Julian