In my workflow, I utilize several metanodes that scrape data from multiple sources. However, there are other parts of the workflow that I intend to execute at a later stage. My concern is that if I run the entire workflow again, it will re-execute the initial metanodes, which take over an hour to complete 
, even though I’ve already completed those steps. How can I manage or control this workflow to avoid redundant execution? 
Hello @mmrostami,
I think important question here is how often and how are you executing your KNIME flows? In general if you leave part of workflow executed running workflow again should work as it start from non-executed nodes.
One possible approach I use is to separate such processes into two (or more) flows. One is to obtain and write data to certain location. Second is to read and use this data.
Hope this helps!
Br,
Ivan
3 Likes
@ipazin That can be, to write data somewhere then use it again in workflow. I noticed KNIME has “cache” node also “Don’t Save Start” and “Don’t Save End” nodes, I tried to use them but still didn’t know how.
@mmrostami have you tried controlling the flow with flow variables?
Another option would be to have sub workflow(s) that you can call also with variables
3 Likes