Try - Catch Error Node in loop

[mlauber71]

@kritsapatw you will need to provide the non-failing path with an alternative (empty table of the same structure).

Error handling (Try - Catch Error) Design Question

OK, so constructed a workaround that could catch the error. I stripped the (very large) example down to a core Metanode where the error occurs. I built an error catcher around that has an alternative table which is deliberately empty but has the same structure as the result. [image] Outside the loop there now is ab End IF node that would take the populated result but insights that both inputs have the same structure. The result from ‘Component A’ is empty due to the caught error so Component …

Catch an error in an optimization loop and continue (Forum 38402) – mlauber71

If you want to just coninue after a fail you will need a different Catch node (the one that catches flow variable errors):

This workflow demonstrates how to use the new Excel Reader and path variables...

also:

Knime 4.4 Cant merge variable stacks! (likely a loop problem)

@joshuash beside what @Thyme is saying these things come to my mind: (especially) with nested loops it can make sense to use Metanodes in order to make sure what part of the loop will do what and how they are wired. You can check „select sope“ by right clicking on the Loop node and see how KNIME would interpret the wiring. it might very well be necessary to check the logic behind the loop and if it would work in every constellation. It might be necessary to provide a dummy table of the same st…