# Queueing Builds

> If you have a large number of ElastiCube builds that are triggered simultaneously, for example, multiple builds running at midnight, Sisense can automatically queue your builds. Sisense queues builds when you exceed the maximum number of concurrent builds, when the current build ends, the next build begins. You can configure the number of maximum concurrent builds in the Sisense Configuration Manager.

*Source: https://docs.sisense.com/main/SisenseLinux/queueing-builds.htm*

---

Last updated: June 11, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Launch     Grow    Enterprise | Cloud     On-Prem |

If you have a large number of ElastiCube builds that are triggered simultaneously, for example, multiple builds
running at midnight, Sisense can automatically queue your builds. Sisense queues builds when you exceed the maximum
number of concurrent builds, when the current build ends, the next build begins. You can configure the number of
maximum concurrent builds in the Sisense Configuration Manager. The default number of maximum concurrent builds is 20.

You can queue up to one build for each ElastiCube, however, there is no limit to how many ElastiCubes can be queued.
Queued builds will begin when the current build is completed even if the current build failed. Sisense will not
execute a build if you cancel the queued build. When a build is added to the queue, you are notified in the build log.

**To define the maximum number of concurrent builds:**

1. Access the Configuration Manager through the **System Management** section of the
   **Admin** page.
   ![Admin SysMgmt Config(7)](https://docs.sisense.com/main/Resources/Images/Admin_SysMgmt_Config(7).png)
2. Under the **/Build** section, enter the value for **MaxNumberOfConcurrentBuilds**.
3. Restart the Build service.
4. Click **Save**. The next time a build exceeds your maximum number of concurrent builds, the build
   will be queued. The UI will present a log message while the build is waiting in the queue.