Call Workflow (Table Based) - execute failure (screenshot inside)

[mlauber71]

From what I understand the “Call Workflow” node at the beginning would call a workflow so this might result in a cascading call. If this is not the intention the you might want to change that.

To be honest I have not fully figured the call workflow business out but I have constructed an example that calls local workflows from a list and is able to iterate that. The data sent back is just a structured information in JSON format but might as well be an Output (Table)

Multiple Workflows

I have created a simple example where you create a table in a parent workflow and then call a sub workflow and read the results back. It is derived from a workflow I use for other purposes (it originated on the KNIME examples server knime://EXAMPLES/50_Applications/08_RESTDemo/01_Call_Local_Workflow) I am not 100% comfortable with all these JSON files and calls but it should work and you can exchange control informations. You might also use the JSON stuff to ‘communicate’ between the workflows,…

Another remark: there should be a log file entry in the central knime.log maybe you could look again if you see something that might give us a hint.

Then there is a Python script in the subworkflow. Initially I do not see why a sub workflow might not be able to handle Python scripts. But do the other sub workflows that work also have Python scripts.