Sometimes when there are parallel branches in a Sematic run (particularly with deep nesting of the branches, it seems), Sematic doesn't always recognize that it can start on a run from one branch while it waits for run(s) in another branch to complete. We should fix this, to make the overall pipeline runtime lower in such cases.
Sometimes when there are parallel branches in a Sematic run (particularly with deep nesting of the branches, it seems), Sematic doesn't always recognize that it can start on a run from one branch while it waits for run(s) in another branch to complete. We should fix this, to make the overall pipeline runtime lower in such cases.