Call Workflow (Table based) on a server - Invalid URI

KNIME Server
1

Hello, I am successfully calling a local workflow using the Call Workflow (Table based) node in my desktop.

But having deployed both workflows onto server the Call Workflow node fails.

I am not using a Server connector node as I was assuming that on the server the workflow is local relative to the parent workflow and both are saved to similar folders relative to the local environment.

Why am I getting the following error:
ERROR Call Workflow (Table Based) 0:2768:2788: Execute failed: HTTP Status 400 – Bad Request
HTTP Status 400 – Bad Request
Status Report
Message
Invalid URI
Description
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Apache Tomcat

2

I have noticed the same sort of issue. When trying to start a KNIME workflow via REST API we getting a bad request error:
<!doctype html>HTTP Status 400 – Bad Requestbody {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}

HTTP Status 400 – Bad Request

3

Hi @Willem ,

This response is expected when e.g. the request body does not match the expected scheme.
There are two end points to execute workflows via REST; a GET and POST endpoint. The GET endpoint should execute and discard a job if you’re looking to simply run a job.

If you wish to configure a job (e.g. timeouts or whether it is discarded), you can create, configure, execute the job. An example workflow to achieve this is here:

Kind regards
Marvin