@<1533619716533260288:profile|SmallPigeon24> , did you try debugging your pipeline locally(steps included)?

I do have 2 initial steps, then one step. However, I abort after the 2 initial steps are done, and I get the "2 experiments aborted."
My third step is ruined because a resource addressed is busy while accessed, which is weird.
Also, when starting the pipeline from a script it starts 2 concurrent runs (experimnt 240 and 241), while it should only start 1.

Hi @<1533619716533260288:profile|SmallPigeon24> , is it possible you're selecting multiple experiments? Or maybe there were two initial steps that were aborted? How does your pipeline look in the UI and do you have something that reproduces that?