we have a pipeline this is configured to execute the runs on a separate server. we're starting to get more usage on it. i originally thought the pipeline was setup such that only one run could execute at once. any subsequent runs would be queued until the first one completed. that's not what's happening. is there some setting to configure this to be the case?

it isnt causing problems for now, since the most i'm seeing 2-3 runs simultaneously. i'd prefer not to see 10 though.

thanks in advance.