> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/branching-baseline/queued-processing-and-concurrent-execution-limit.md).

# Queued Processing and Concurrent Execution Limit

**Product:** AutoRABIT ARM\
**Module:** Version Control – Branch Baseline\
**Availability:** Classic UI and New UI

### Overview

AutoRABIT ARM has enhanced the **Branch Baseline workflow** by introducing queued processing to improve application performance and prevent multiple baseline operations from running simultaneously.

With this enhancement, a maximum of **2 Branch Baseline operations can run concurrently per customer**. Any additional requests are automatically added to a queue and processed as execution slots become available.

### What's New?

#### 1. Concurrent Baseline Execution Limit

* Each customer(Org) can run up to **2 Branch Baseline operations simultaneously**.
* When two baselines are already running, additional requests are automatically placed in a queue.
* Queued requests start automatically when an execution slot becomes available.

#### 2. Queue Visibility and Management

* Users receive a **Queued** status when a baseline request is waiting for execution.
* Users can view their pending Branch Baseline requests in the queue.
* Queued requests can be cancelled before execution.
* Running baseline operations can also be cancelled.

#### 3. Automatic Queue Processing

* Queued requests are automatically picked up when execution capacity becomes available.
* Queue processing may take approximately **40–60 seconds** to start a pending request after a slot becomes available.
* Pending requests are retained during ARM restarts and resume processing afterward.

### How It Works

1. Navigate to **Version Control > Branch Baseline**.
2. Initiate a new Branch Baseline operation.
3. If fewer than two baselines are running for your account and execution capacity is available, the request can start processing.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPnVTlC2nFM8jENK4Cl1l%2FScreenshot%202026-11-06%20at%2023.07.12.png?alt=media&amp;token=35709b8f-ad0f-4985-ba7f-e8dbe77e6f24" alt=""><figcaption></figcaption></figure>

4. If the concurrent execution limit has been reached, ARM places the request in the queue and displays a **Queued** message.
5. Users can monitor or cancel pending requests from the queue view.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FZpQt4HsArZpttQQ6aZ5O%2Fimage.png?alt=media&amp;token=e93de589-4a63-4a1e-872f-cf848a3abc45" alt=""><figcaption></figcaption></figure>

6. ARM automatically starts queued requests as execution slots become available.

### Important Notes

* The default concurrent execution limit is **2 Branch Baselines per customer**.
* Additional requests are queued automatically; users do not need to resubmit them.
* Queued requests may take up to approximately one minute to begin processing after an execution slot becomes available.
* The concurrent execution limit can be adjusted through configuration when required.
* Existing restrictions on running duplicate baselines for the same repository and branch remain unchanged.
* This enhancement does not change the baseline content, metadata retrieval, or resulting branch configuration.
* The functionality is available in both **Classic UI and New UI**, subject to feature enablement.

### Benefits

* **Improved System Performance:** Prevents excessive simultaneous baseline operations.
* **Automatic Queue Management:** Processes additional requests without manual intervention.
* **Better Visibility:** Allows users to monitor and cancel queued baseline requests.
* **Improved Reliability:** Retains pending requests during system restarts.
* **Consistent Experience:** Provides the same queued processing behavior across Classic and New UI.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/branching-baseline/queued-processing-and-concurrent-execution-limit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
