> 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/troubleshoot/known-issues-limitations/arm-known-issues.md).

# ARM Known Issues

These are the known issues in **ARM® 22.2**.

### Vlocity Known Issues <a href="#vlocity-known-issues" id="vlocity-known-issues"></a>

These are the known issues for vlocity in this release.

**"Autodraft" or "Select Manaully" feature in EZ-Commit screen timed out**\
For massive retrieval of **Vlocity** data packs, Auto-draft or Select Manually functionality has more chances to get timed out.

**Logs contain "undefined message" for Vlocity commits**\
This known issue can be considered from the Vlocity build tool rather than from ARM because for the log report that contains 'undefined message', such log error messages are being returned from the Vlocity build tool only. Currently, [ARM](https://www.autorabit.com/products/automated-release-management/) is working with the Vlocity tool to fix the issue as soon as possible. Stay tuned for more updates.

### EZ-Merge Known Issues <a href="#ezmerge-known-issues" id="ezmerge-known-issues"></a>

**Issue:** The following error causes **EZ-Merge** to fail: `Cannot delete <metadata_type>; <metadata_components> must be deleted invidually`

**Reason:** ARM is unable to identify the deleted components from the `<metadata_type>`.

**Explanation:**\
Let's assume **Branch 1** has workflow components, *workflow 1* and *workflow 2*; **Branch 2** is a child of **Branch 1** and has same components as **Branch 1** i.e., *workflow 1* and *workflow 2*.\
If *workflow 1* and *workflow 2* are deleted from **Branch 2**, and merge is done from **Branch 2** to **Branch 1** with **Run Destructive Changes** checkbox selected, EZ-Merge prevalidation will fail with error: `Cannot delete <metadata_type>; <metadata_components> must be deleted individually.`\
This happens because the deleted workflow details are not retained in the application for validation.

**Sample image attached:**

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkyAVyOkYdRvYpQM9mW3n%2Fimage.png?alt=media&amp;token=51ef0176-dffd-4e83-824d-2ab6dc0d54bc" alt=""><figcaption></figcaption></figure>

**Workaround:** If you see the aforementioned issue, please avoid selecting the **Run Destructive Changes** checkbox under the **Prevalidate Merge** section.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdhQZkPFk50hi1pfgET9p%2Fimage.png?alt=media&amp;token=75d8a9da-a031-447f-9e72-500a163fe713" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/troubleshoot/known-issues-limitations/arm-known-issues.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.