Trigger Task Option

[ndayalani21]

In the Trigger Task; there is an Option Do not start a new execution if one is already active

In the Documentation this option Do not start a new execution if one is already active allows you prevent a Pipeline from running again if a previous execution of that Pipeline is already running.

Does this option ignore the second request if it is sent at the same time or does it queue it up?

[tlikarish]

If the option is enabled and concurrent requests are made, then it is possible for both requests to start a pipeline executing. The feature was originally only for tasks that were scheduled, which is why this only prevents another one from starting if there is already one running.

Although, we’ve heard some feedback about changing the behavior such that only one trigger task could start even if there are multiple requests made simultaneously, so might be looking into that soon.

[ndayalani21]

So if this option is enabled and concurrent request are made; will it ignore the second request or does it queue it up?

[tlikarish]

If the requests are made close enough together, then both requests will queue up and start executing.

[cstewart]

If it is essential to ensure that only one runs at a time, you could use the public API to find out if one is already running, or use some other method to gate execution.