Found the thread I was looking for. This is more about having the workflow handling the scheduling vs having the scheduler:
As per my comments there:
I see a few drawbacks such as:
- Your workflow would constantly be running, and looping infinitely. I am not sure how efficient this is, not to mention that it would be using resources constantly.
- What happens if the workflow is somehow stopped? What would re-trigger the workflow?
- It would mean to have Knime open all the time. What if you need to restart Knime? What would re-trigger the workflow?
- Based on what you explained, you are expecting the workflow to be reset by the workflow itself. I don’t think that this is possible.
With the task scheduler:
- Your workflow does not have to keep running, therefore will only use resources whenever it runs.
- You do not have to worry about manually triggering or re-triggering the workflow.
- You can restart your Knime independently, and not to worry about manually triggering or re-triggering the workflow.
- Each trigger via the command line is a new execution and has the option to reset the workflow before executing.