Common Errors and Resolutions
Last updated
Was this helpful?
Last updated
Was this helpful?
Users may encounter a 413-status error in the browser console when trying to upload duplicate profile files that have been resolved after downloading from version control. This occurs when users try to download numerous files at one time. Download one profile file at a time to resolve the error.
This error may occur when users are selecting an ALM on the EZ-Commit screen. VPN connectivity appears to be the source of intermittent ALM connectivity issues; the ALM is incorrectly configured. To correct this issue:
On the My Account screen, look for the ALM configuration.
To reauthenticate your ALM configuration, click the Test Connection icon to verify your credentials.
If the steps above do not work, create a new credential and link it to your ALM account.
Users may encounter this error message when trying to register the Bitbucket repository. This occurs when:
The Bitbucket account is locked.
When registering the Bitbucket repository, the wrong credentials were used.
The IT/Network team has whitelisted ARM's IP address.
To resolve this issue:
Try recreating a new credential and updating the credentials under the Admin > Credential section.
Re-register your bitbucket repository in ARM.
The error below pops up while selecting the org for merge validation: cvc-elt.1.a: Cannot find the declaration of element 'web:validateSalesforceOrgConnection'
Cause of the issue: This may be due to a cache problem while selecting the Salesforce Org.
Resolution: Clearing the browser cache and refreshing the browser will resolve the issue.
When running a CI job, if any of the folders in the remote repository has an empty JSON file, that will cause SFDX commands to fail with an incorrect JSON error. Delete the empty JSON file(s) from the remote repository to resolve this issue and re-run the CI job.
This error typically happens when you try to push to a remote repository, but your local branch is behind the remote branch. You need to pull the latest changes from the remote repository before you can push your changes.
This error usually occurs when you try to push a commit to a target branch, but the HEAD has been updated by someone else after you started your merge. You need to fetch the latest changes from the remote repository using git fetch and then merge them into your local branch using git merge before attempting to push again. You can’t re-push because:
Your merge commit references an older state of the target branch.
Re-pushing would skip newer commits, which could cause lost work or conflicts.
You need to re-perform the merge using the latest version of the target branch.
This error may be encountered while attempting to commit changes for a production organization to the GitHub master branch. This occurred because protected branches do not allow force-pushes. Get in touch with your Administrator to turn off the protection on that branch.
Multiple Branching Baseline jobs show no local modifications to commit. As a result the following error message is thrown. This occurs when one of your commit messages is missing a valid issue key:
9b4c80c: Commit From AutoRABIT [Branch Baseline] [LabelName:UAT2 Baseline]
Cross-verify the following things:
Create a new repository link where the key should include part of the commit comment from AutoRABIT or
Modify the existing Repository Link’s Key to align with the AutoRABIT Branching Baseline commit comment or
Disable the Repository Link.
When a deployment fails, this error usually occurs due to behavior in the Salesforce CLI 7.83 version. When retrieving the LWC components, it retrieves .css-meta.xml rather than .js-meta.xml file, which results in the deployment failing. Try renaming the .css-meta.xml file to .js-meta.xml and running the deployment again. Salesforce stopped maintaining SFDX v7 in April 2023 and no longer provides updates, bug fixes, or technical support.
This issue will occur if there are any special characters like the one below and if the string (length=7) is considered a GIT conflict (it is a GIT behavior), it will not perform the Merge.
Special Characters: '>' ; '<' ; '|' ; '='
We recommend limiting the above four special characters to fewer than 7 to avoid such problems.
For example, in the Class file, if you observe this ">>>>>>>" character string (length=7), then update it to less than 7 in the branch itself and rerun the Merge operation.
In CodeScan Cloud, the default setting for unit test timeouts is 1 hour (3600 seconds) for limited Metadata analysis. These timeouts might not be enough if your project has a lot of metadata. This is the reason behind the error message.
Increase the timeouts to avoid this problem:
Click Project Settings > General Settings in your Project Overview.
Click the CodeScan tab on the left and modify the timeout under the Unit Test Timeout once you're in General Settings.
There are several possible explanations for AutoRABIT to throw an error "local and remote repo is not on same revision":
The local repository is out of date.
The branch that contains the commit was deleted, so the commit is no longer referenced.
Someone force-pushed the commit.
This error message occurs when performing a merge when credentials are not properly mapped in ARM. Follow the steps below to resolve this issue.
In Azure, create a new token.
In ARM, go to Admin > Credential and create a new credential.
Re-test the connection after mapping the credential to your version control branch (in the Profile section).
If the test connection for the mapped repository and branch fails, we recommend upgrading your password and altering the credential in the credential section, then retrying the connection.
Users may encounter this error when trying to register a Salesforce environment in ARM. This occurs when users do not use the My Domain URL when adding the Salesforce org to ARM. To correct this error, use My Domain URL while registering a Salesforce org in ARM.
Users may encounter this error when trying to connect to the Bitbucket repo, which typically relates to user permissions. If you are using the wrong file format for the package.xml, then the above error occurs. Check the permissions you have on your Bitbucket repository with the repository owner/administrator. Request permissions other users have if you don't have the needed permissions.
This error is usually returned when you have some branch restrictions set up in your repository and the commit you are trying to push does not meet the requirements of that branch restriction.
The potential causes of Picklist not found error-related Merge/Commit Prevalidation deployment failures are listed below, along with the procedures you need to follow to fix them:
Verify the field name: Verify the API name or the label of the picklist field you're trying to reference and the spelling and capitalization of your source.
Check the object: Verify the object you're working with has the picklist field you're looking for. Locate the proper object by going to the Object Manager in Salesforce Setup. Look for the disputed field in the Fields & Relationships section in the target org.
Validate field-level security: Make sure the user or profile you're using can see and access the picklist field. Ensure the user has the appropriate permissions to see and update the field by checking the field-level security settings for their profile. Check the field-level security settings to ensure the user's profile has appropriate permissions to view and edit the field.
Consider record types: If your Salesforce org utilizes record types, check to see if the picklist field is specific to a particular record type. If it is, ensure that the user or profile you're using has access to the relevant record type.
Consider field dependencies: If the picklist field has any field dependencies or controlling fields, ensure that the controlling field values are set correctly. If the controlling field values are incorrect or incompatible, it can lead to the "picklist field not found" error.
This error occurs when you try to push to the branch you currently have checked out. To resolve this, you can either switch to a different branch or create a new branch to work on.
This error is often related to network issues or server misconfigurations. It can occur when pushing large files or when the Git server is experiencing problems. Checking your network connection and trying again later may resolve this error.
Suppose the error REJECTED_NONFASTFORWARD is thrown in your EZ-Commit; in that case, the issue is specific to your repository, and the error occurs at the GIT version control level when multiple developers try to modify a file simultaneously. If you reencounter this issue, please wait a few minutes and reattempt the commit.
Users may encounter this error when a merge is failing for metadata members. This is due to an invalid structure. If there are any special characters like '>', '<', '|', '=', and the string(length =7), this is considered a GIT conflict (a GIT behavior), which will cause the merge to fail. To prevent this, we recommend that you limit the previously mentioned unique characters to less than seven (7).
For example, if you observe ">>>>>>>" character string(length =7) in any of the Apex Class files or any metadata member files, then update it to less than 7 in the branch itself and re-run the Merge.
Users may encounter this error when trying to perform a merge due to invalid characters like (>>>, <<<) symbols used in the file. To resolve, download the merge conflict files and validate the characters present in those XML files.
When a commit returns this error, it is either because:
Version control mapped to your Salesforce org user is incorrect.
Your user credentials are incorrectly configured in ARM.
Ensure your account is correctly mapped with the version control branch to reflect the commits under your name.
Verify your credentials in the Admin > Credential Manager section and authenticate the connection again.
This error occurs when you try to push a branch that doesn't exist locally or has a different name. Ensure that the branch exists and that you have the correct name.
This error may be encountered while attempting to commit changes for the production organization to the GitHub master branch. This is expected. When the branch is set with the branch policy, you cannot push it directly and need to create a pull request to update it. Once you remove the branch policy, you should have the ability to push changes to the master branch. Please contact the GitHub Administrator to request push permissions.
When generating a code coverage report for a registered Salesforce org, the test fails with this error if the Apex test execution takes a long time. Go to TAF > Apex Test Execution and clear all of the tests in the queue, then run the code coverage report through ARM again.
This error may be encountered when a user tries to access the Salesforce Org in the ARM Version Control, CI Jobs, Deployment, and SFDX Modules. This may occur due to an invalid username, password, or security token, if the user is locked out, or if the Salesforce API version is incorrectly configured.
Upgrade the API source flow in your Salesforce org to the most recent version and maintain the same Salesforce version in ARM by going to Admin > My Account > My Salesforce Settings and updating the API version.
This occur may occur when environment provisioning jobs are failing due to using the wrong file format for the package.xml file. Upload the correct package.xml file during the creation of environment provisioning jobs.
Users may encounter this error message when a Merge is failed. This occurs when repository credentials are expired or have been modified and not updated in ARM.
Navigate to Admin > VC repos, select your repository, and perform a test connection. Please verify your repository credentials are not expired or modified.
Re-run the CI job after you confirm that the repository connection is successful.
This occurs when using an old version of CodeScan. Install the most recent version of CodeScan to avoid any installation errors.
This error occurs during the branching baseline operation when version control credentials are insufficient for pushing changes to a branch. This indicates that you have read permissions but not write permissions. After updating your permissions, re-run a new branching baseline operation.
This error message indicates that your local branch has commits that haven't been pushed to the remote branch. To resolve this, you can either push your local commits using git push or discard your local commits using git reset or git stash.
If you are unable to connect to the ARM instance and get this error, it is due to cache and cookies in your system. To resolve this issue, follow the steps below.
On your computer, open Chrome.
At the top right, click More.
Click More tools.
Clear browsing data.
At the top, choose a time range. To delete everything, select All time.
Next to Cookies and other site data and Cached images and files, check the boxes.
Click Clear data.
Now, log in to your instances using the new browser tab.
For more content, refer to.
For detailed information on how to change the timeouts, click .
Please refer to this article,
Please refer to this article:
Please refer to this article,
This error mirrors the "" error noted above. Please refer to the steps above for resolution.
