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.
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 B will be chosen.
kn_forum_vol_trader_simple.knwf (598.3 KB)