Little update. To place the DB Connector and Transaction very close to the DB Inserter in the Metanode, the first iteration works fine until the Loop End Node.
Encountered loop-end without compatible head! This can be like a “Syntax Error” if some nodes starting in the loop and their connection will stopped/terminated outside the loop. Maybe I’m a little bit blind. Where is the connection which goes outside the loop. I can’t see it.
I also checked my flow variable. There is hint that I loose variables fater disconnect from the database
Interessting option. Because of the IF Switch the second input port is inactive an then the complete End Loop node is inactive. I tested your solution Table Row to Variable → Active Branche Inverter → Variable to Table Row. Unfortunately I got the same error message “Encountered loop-end without compatible head!”
If the Loop End node looses the connection to the Loop Start node I tried to connect the variable output port from the Table Row to Variable Loop Start node directly to folw variable input port of the Loop End node with the same result. What’s happening with the DB connection and the Flow Variables in a loop?
Where I have written the two “NoOp” nodes, if you have the NoOp nodes from NodePit Power Nodes (nodes that do nothing but can help structure the flow), then place them at the points indicated by the blue/yellow boxes and attach the flow variables to them.
If you don’t have NoOp nodes, then place an “Add Empty Rows” node at those two points and configure to “add 0 rows” (i.e. do nothing!).
Your workflow currently has portions of the database processing attached regardless of the IF switch branch chosen, whereas you only want that active with the upper branch. This could cause unexpected behaviour when the flow variable from the Connection Closer (which should only operate on the upper IF branch causing the End If to be bypassed and arriving at the Loop End.
By using “noop” (or equivalent) nodes, it better controls the correct flow from the IF Switch.
had a similar problem in the past with loops and DB Transaction nodes. Not sure if it was fixed, but what you could try is to put the DB transaction nodes inside a component, like described in this thread:
