sorry, right, I meant for us, not necessarily for you. we also have lots of states, but there are specific ones that in particular bomb out when >N are running at the same time.
So the combination of setting the pool size and controlling execution order could be helpful for us, though I’m assuming the feature was added more around dependency order, with the bonus of also, say, in this case, making sure lower envs run before production for certain types of changes.