Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: stonysmithIn this example, (and when running in BRE) it makes sense to have an indication that a node has been "queued for execution".
=====
Upon first reading your request, I thought you wanted to know which node is "next".
When you have a much more complicated set of relationships between the nodes, the decision as to which node is to be run "next" is not made until at least one of the currently running node(s) finish.
Let's say you have two strings of nodes:
A-B-C
D-E-F
and that you click run on all of them at once. All six of them would be "queued for execution".
However, the decision of whether to run B or E first is dependent on which of A or D finishes first.
The determination of "next" is not made until something finishes, and then the controller re-examines the entire execution queue.