Support Pipeline-Level Execution Concurrency Limits with Queueing
pending feedback
P
Purring Bee
Description
The customer has requested support for pipeline-level execution concurrency limits with execution queueing to better control high volumes of pipeline executions.
Use Case
The customer's CD pipelines are triggered by AWS Auto Scaling Groups, which can generate a large number of pipeline executions simultaneously. This results in significant delegate resource consumption and increased infrastructure costs.
The customer is looking for a mechanism to throttle execution at the pipeline level while ensuring all executions are eventually processed.
Requested Functionality
Configure a maximum concurrency limit for an individual pipeline.
Queue any executions that exceed the configured concurrency limit instead of rejecting or running them immediately.
Automatically start queued executions as active execution slots become available.
Enhancement Request
The customer also requested consideration for a dynamic concurrency model that adjusts the allowed concurrency based on available delegate capacity.
Example:
1 delegate → 20 concurrent executions
2 delegates → 40 concurrent executions
3 delegates → 60 concurrent executions
This would allow execution throughput to scale automatically with available delegate capacity while preventing sudden execution spikes from overwhelming delegate infrastructure.
Customer Benefits
Prevent delegate resource exhaustion during traffic spikes.
Reduce delegate infrastructure costs.
Improve deployment stability during burst workloads.
Enable automatic scaling of deployment throughput based on delegate availability.
Log In
a
abhijit.pujare
updated the status to
pending feedback
a
abhijit.pujare
We currently support the capability to have concurrency limits at the project level: https://developer.harness.io/docs/platform/pipelines/configure-per-project-concurrency/#execution-behavior. Would this possibly solve your use case?