> 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/salesforce-known-limitations/sfdx-limitations.md).

# SFDX Limitations

## Salesforce DX Known Issues <a href="#salesforce-dx-known-issues" id="salesforce-dx-known-issues"></a>

These are the known issues for [Salesforce DX](/product-guides/arm/arm-features/salesforce-dx.md) in this release.

**Failed to initiate deployment**\
If a process is added to Salesforce's queue for more than 30 minutes during the deployment of CI Jobs with SFDX Repo as the source, the error **"Failed to initiate deployment"** is returned.

## Salesforce DX Known Limitations <a href="#salesforce-dx-known-limitations" id="salesforce-dx-known-limitations"></a>

Below are the limitations of ARM related to salesforce dx:

1. [Salesforce DX](https://www.autorabit.com/blog/the-basics-of-salesforce-dx/) functionality is currently applicable only for DX-enabled version control repositories.
2. Source commit from EZ-Commit process will be done only in DX-format for SFDX enabled repositories.
3. It is mandatory to select the **SFDX Package Directory** for DX-enabled repositories while carrying out the EZ-Commit operation.
4. Dependencies will be calculated using **Salesforce Dependency API**.
5. Adding dependencies are subject to the **API limitations**.
6. In **SFDX > Modularization**, the data will be extracted only if the **CustomObject** metadata either selected/identified as a dependency.
7. A new package version gets generated each time the packages get updated. However, if you would like to install the updated packages to the same Salesforce org, the packages will not get installed. To do so, uninstall the current package from the Salesforce org and install the latest one **(Custom Deployment)**.
8. For a module or an unlocked package creation request is in progress, make sure for the same repository and branch, another creation request is not submitted.
9. The user should not include such metadata members in a package directory of a branch if the same metadata members are already available for another package directory for the same branch.
10. Profiles will not be included in the **Unlocked Packages**.
11. Listed below in the table the metadata types which are currently not supported in the DX format:

| AccountRelationshipShareRule | AnalyticSnapshot           | Audience           |
| ---------------------------- | -------------------------- | ------------------ |
| AccountRelationshipShareRule | AnalyticSnapshot           | AssessmentQuestion |
| AssessmentQuestionSet        | Audience                   | ApexTestSuite      |
| AIApplicationConfig          | BlacklistedConsumer        | CMSConnectSource   |
| CustomIndex                  | AIApplication              | ForecastingType    |
| ForecastingFilter            | ForecastingFilterCondition | InboundCertificate |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/troubleshoot/known-issues-limitations/salesforce-known-limitations/sfdx-limitations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.