Workflow Execution with Wait Nodes

Hi KNIME Community,

I am currently working on a workflow designed to read an Excel file that serves as a trigger list for multiple countries.
1

The process involves:

  1. Reading the GvN Trigger List Excel Table: This table indicates whether a workflow for a specific country should be executed, based on whether the “Complete” column is tagged as “YES”.

  2. Executing Workflows Conditionally: If a country has “YES” in the “Complete” column, the corresponding country workflow is triggered using the Call Workflow Service node


    2

  3. Managing Heap Space and Execution Order: Some country workflows consume more heap space than others, which led me to include a Wait node to ensure the workflow runs sequentially without overloading the system.

Questions:

  1. Are there any recommendations or best practices for optimizing this type of workflow process? Specifically, is there a more efficient approach for reading the Excel table and conditionally executing workflows? (Initially the current process will be scheduled to run daily in the Server so that it will check daily if there are “YES” tagged in the excel file)
  2. How does the Wait node operate when the workflow is scheduled to run daily? Does it ensure that each country workflow completes before proceeding to the next, or is there a way to force sequential execution one country at a time based on the order in the Excel table?
    ff: Given that some workflows consume more heap space than others, is there a way within the current setup to ensure only one country workflow runs at a time? For example, can the process run through the table row-by-row, executing one workflow and waiting for completion before moving to the next?

Any insights, suggestions, or examples of similar workflows would be greatly appreciated.

Thank you!

@Heldyyyyy you might want to take a look at the concept of loops which should provide most of the functions you want:

3 Likes

Thank You @mlauber71 will check this out!