Select Language:
If you’re seeing an error message that says “Cannot have more than 0 builds in queue,” it likely means there’s an issue with your CodeBuild project settings. Specifically, your project may have the concurrent build limit set to zero, which stops any builds from running.
In AWS CodeBuild, there are two important limits to understand:
– The account-level quota: This is the total number of builds your account is allowed to run at the same time in a given region. For example, your account might be limited to 10 simultaneous builds.
– The project-level limit: Each project can also have its own limit on how many builds can run at once. If this is set to zero, no builds will be allowed for that particular project, no matter what the account quota is.
The error you’re seeing suggests that your specific project has its concurrent build limit set to zero. This prevents any builds from starting or queuing, even if you have available capacity at the account level.
To fix this, follow these steps:
1. Sign in to the AWS CodeBuild console in the region you’re working in.
2. Find and select your build project.
3. Look for the setting that controls the number of concurrent builds, often labeled something like “Restrict number of concurrent builds this project can start.”
4. If this setting is enabled and set to zero, either disable it or increase the number to a value within your account limit (up to your maximum of 10, if that’s your account quota).
Remember that when your builds exceed the available capacity, they will go into a queue. The maximum number of queued builds can be five times your project’s concurrent limit. Also, if builds stay queued beyond the default timeout of eight hours, they will be removed from the queue.
If adjusting the project settings doesn’t resolve the problem, consider reaching out to AWS Support. They can help you check if there are any account-specific restrictions affecting your builds.
This approach should help you get your builds running smoothly again.





