Does “Number of concurrent builds” apply to GitHub webhook deployments?

[roshangeek435]

I just want to say thanks for building Coolify. it’s been awesome for managing and deploying multiple projects from one server.

I’ve noticed a difference between manual deployments (triggered via the Coolify dashboard) and GitHub webhook-triggered deployments when it comes to the “Number of concurrent builds” setting under Server → Advanced.

When I manually trigger multiple deploys at the same time for example, by clicking “Deploy” on multiple projects or using “Deploy All” the concurrency limit works exactly as expected.
If I set it to 1 or 2, Coolify only runs that many builds simultaneously, and queues the rest until the active builds are finished.

However, when a GitHub push triggers multiple applications connected to the same repository (via webhooks), the concurrency limit does not apply. All projects start building at the same time, regardless of the number set in the “Number of concurrent builds” box.

This can cause very high CPU and memory usage (especially on EC2 instances) when multiple apps deploy at once from a single push.

❓My question

Is that the expected behavior right now?
Or should webhook builds also respect the “Number of concurrent builds” limit like manual ones do?

If it’s not supported yet, it’d be really helpful if webhook-triggered deployments could also follow the concurrency limit — basically queueing up builds instead of launching them all at once.

Adding this feature would make multi-app setups a lot smoother and prevent the server from getting overloaded when several projects deploy together.

Thanks again for all your work — Coolify’s been a game changer 🙌