@SeanP You’re correct that simply chaining nodes won’t do anything. That is exactly why I started the topic about Transactions nodes and not chaining actions with ‘wait for’ nodes.
Nevertheless (you state the same thing I believe) nodes still need to be chained with the transactions nodes in between for a script to act as a multiple scripts and execute actions based on the result of previous executions within the same graph. The order is then give by the chaining.
With this in mind, I made it work and this is the order of actions as I would imagine.
If I remove the second transactions sequence (node 9) then the script fails because despite the fact the the first transaction sequence (create sheet) is excluded in it’s own start and end nodes, there is a sort global transactions that executed parallel to the one of sheet. That’s why if I remove node 9 the script fails. It’s not excluded and so it’s can’t see the sheet that just was created.
I’m not the developer so chances are that I’m wrong. But I still state what I think so that the devs would finally correct us and say how the order is actually executed.