Looking at your screenshot I want to make you aware of the following: If you use the Table Row to Variable node, it will turn the first row into a variable only.
In order to process both paths you’d have to iterate over the table using e.g. Table Row to Variable Loop Start Node.
I think if you indeed go with an approach that calls a different workflow (e.g. via Call Workflow Service node) you may be able to go with minimal “conditional” logic inside your loop (pretty much just the “routing logic” that determines which workflow has to be called) and provided that the Call Workflow Service Node does not have to return an output that is processed in your caller workflow, any looping delay may be negligible.
Here’s a very minimal example…
CallerCallee.knar (243.9 KB)
Edit:
I actually just tested this and it looks like even if you don’t expect something to be returned the loop still only continues once the workflow you call finishes…
Right now I am actually not sure how to make it work that both processes happen in parallel.