When the pipeline executes multiple parallel options, it automatically switches to the first option.

Option arguments are added to the pipeline, but when actually executed in parallel, it looks like there are at most three.If so, the next Option will automatically jump to the first Option.Is this a bug or something?


Start by reproducing the pipeline with more than three parallel options and compare the configured options with those executed. Confirm whether later options switch back to the first option, then document the execution behavior that should be considered fixed.

Written by the indexing model from the issue text.