Continuing the discussion from Call the workflow table based on the variable that does not accept with the path:
Is it possible to save the workflow execution executed in the Workflow Executor node?
Thx
@cridiaz what you could do is omit the “-nosave” option and then zip the workflow with a timestamp. You just might have to make sure that it will be reset at the start of the next round.
Ok thanks @mlauber71 but let me explain better I batch launch a wkf with the -nosave option omitted, this wfk does some processing and then inside it through the Workflow Reader and Workflow Executor nodes I launch a second wkf called LK_ I wanted to know if it was possible to save also the execution of LK_ because at the moment I don’t see it, maybe I have to put the Save Workflow node?
@cridiaz I think you could try and employ the concepts of integrated deployment and maybe save your workflow under a name with a timestamp. What you might want to notice is that sometimes it seems that within batch local path variables might not work as expected and you might want to provide a path via a workflow or a static variable.
Blog: An Introduction to Integrated Deployment
KNIME Collections: Getting started with Continuous Deployment for Data Science (CDDS) for Business Hub
KNIME Integrated Deployment Guide
https://docs.knime.com/latest/integrated_deployment_guide/index.html
1 Like