---
title: Why are my Vercel builds queued?
description: Learn about why your Vercel builds may be getting queued and how to resolve this.
url: /kb/guide/why-are-my-vercel-builds-queued
canonical_url: "https://vercel.com/kb/guide/why-are-my-vercel-builds-queued"
published: 2025-11-03
last_updated: 2025-11-10
authors: Allen Hai
related:
  - /docs/deployments/managing-builds
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---
<!-- docsgraph:related -->
## Related pages

> **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below.

- [Build Queues](https://vercel.com/docs/builds/build-queues?from=related) — Understand how concurrency and same branch build queues manage multiple simultaneous deployments.
- [Managing Builds](https://vercel.com/docs/builds/managing-builds?from=related) — Vercel allows you to increase the speed of your builds when needed in specific situations and workflows.
- [Builds](https://vercel.com/docs/builds?from=related) — Understand how the build step works when creating a Vercel Deployment.
- [Troubleshoot Build Errors](https://vercel.com/docs/deployments/troubleshoot-a-build?from=related) — Learn how to resolve common scenarios you may encounter during the Build step, including build errors that cancel a depl
- [Monorepos FAQ](https://vercel.com/docs/monorepos/monorepo-faq?from=related) — Learn the answer to common questions about deploying monorepos on Vercel.
- [Why aren't commits triggering deployments on Vercel?](https://vercel.com/kb/guide/why-aren-t-commits-triggering-deployments-on-vercel?from=related) — Commits not triggering deployments on Vercel? Walk the diagnostic checklist covering authentication, commit author acces
- [Can you deploy based on tags/releases on Vercel?](https://vercel.com/kb/guide/can-you-deploy-based-on-tags-releases-on-vercel?from=related) — Learn how to deploy based on tags/releases on Vercel.
- [How can I use the Vercel CLI for custom workflows?](https://vercel.com/kb/guide/using-vercel-cli-for-custom-workflows?from=related) — You can use the Vercel CLI to deploy any application, including custom git providers and restricted source code.

Full cross-link map for this page: [/kb/guide/why-are-my-vercel-builds-queued.graph.md](/kb/guide/why-are-my-vercel-builds-queued.graph.md)
<!-- /docsgraph:related -->


To make Deployments, the Vercel platform must first build a project. Building projects in the cloud is much faster than building locally, however, it is possible for builds to get queued when making multiple deployments at the same time.

## Concurrent Builds Limit

By default, Vercel accounts have access to a **single concurrent build slot**. This means that only a single deployment can be building at any one time **unless additional concurrent build slots are purchased**. The maximum number of concurrent build slots is dependent on the account plan, this is shown below:

- Hobby (1)
  
- Pro (12)
  
- Enterprise (Custom)
  

## Adding Concurrent Builds

It is not possible to increase the number of concurrent build slots available for Hobby accounts, if your project would benefit from additional build slots, you may wish to consider upgrading to a Pro team plan.

Additional concurrent build slots can be purchased for **Pro team plans** from the [Vercel Dashboard](https://vercel.com/). To do so, select the Pro team you wish to add the additional build slots to from the team picker in the header. Then, click "Settings" and select the "Billing" section.

From the "Billing" section, find the fieldset labelled "Concurrent Builds" and enter the total number of build slots required before clicking "Confirm". The fieldset is shown below:

Enterprise teams can add concurrent builds as part of their plan with Vercel, or make use of [On-demand concurrent builds](https://vercel.com/docs/deployments/managing-builds#on-demand-concurrent-builds) to add slots as and when they are needed.

## Multiple commits on a single branch

Commits to a single git branch work slightly differently and aren't affected by how many concurrent builds your team has. When committing to a branch, only one commit on that branch can be built at a time, even if you have more concurrent builds purchased.

With each new push, if Vercel is already building a previous commit on the same branch, the current build will complete and any commit pushed during this time will be queued. Once the first build completes, the most recent commit will begin deployment and the other queued builds will be cancelled. This ensures that you always have the latest changes deployed as quickly as possible.

> _Enterprise users can use_ [_Urgent On-Demand Concurrency_](https://vercel.com/docs/deployments/managing-builds#urgent-on-demand-concurrent-builds) _to skip the Git branch queue for specific runs. However, this queue will still apply to_ [_project-level On-Demand Concurrency_](https://vercel.com/docs/deployments/managing-builds#project-level-on-demand-concurrent-builds)