# Cloud Errors and Solutions
## CodeScan Cloud
## Common Errors and Solutions
### Can the status of issues marked as False Positives in the lower environment be transferred when the scan is triggered in the higher environment?
Issues in standalone branches are treated separately. The status can only be transferred if the Develop branch is a comparison or pull request branch using ProductionReady as the target.
### Why am I getting the error 'Background tasks failing'?
This error either occurs if it’s out of memory or when multiple analyses have been triggered at the same time. The analysis triggered last gets completed first.
CodeScan is based on SonarQube™, an open-source reporting platform for coding languages. The Background Tasks that occur when an analysis report is run have been added by SonarQube™ to allow administrators to view technical details about why the processes fail.
To learn more about background tasks, please see the [SonarQube Documentation - Background Tasks](https://docs.sonarqube.org/latest/analysis/background-tasks/).
### Why am I getting the following error: 'Error during SonarScanner execution'?
Why is my Commit and Merge failing with the following SonarScanner error but still allowing submission: '**Language of file force-app/main/default/permissionsets/abc\_filename.permissionset-metaxml**' cannot be decided as the file matches patterns of both sonar.lang.patterns.mule: \*\*/\*abcd,\*\*/\*xml and sonar.lanq.patterns.sfmeta: \*\*/\*profile-meta.xml.\*\*/\*permissionset-meta.xml.\*\*/\*settings-meta.xml.\*\*/\*object-metaxml.z\*/\*field-meta.xmll\*s/\*flow-meta.xml.\*\*/\*sharingrules-meta.xml.\*\*/\*workflow-meta.xml\*\*/\*profilesessionsetting-meta.xml \*\*/\*profilepasswordpolicy-meta.xml.\*\*/\*.profile，\*\*/\*.permissionset，\*\*/\*.settings.\*\*/\*.object.\*\*/\*.flow，\*\*/\*.sharingrules，\*\*/\*workflow\*\*/\*.profilesessionsetting，\*\*/\*.profilepasswordpolicy'?
**Environment configuration checklist**
Configure the Mule setting (Key: sonar.mule.file.suffixes) with values ".abcd" and ".xml," which are causing errors. Navigate to the project where this error occurs in CodeScan. Go to **Project Settings > General Settings**, and search for "mule" in the search box. Remove ".xml".
By adjusting these settings in CodeScan, the SCA will not fail.
### Why am I getting an 'Expired Token' error on my project analysis?
Errors such as **Expired Token** on your **Project Analysis** page can sometimes be fixed by resetting the link to your code repository. CodeScan Cloud allows you to do this *without erasing* the historical data present in your project.
To fix the above errors, follow the steps below to delete the **Analysis Project:**
1. Go to your **Project** and navigate to the **Project Settings > Project Analysis** page.
2. Click on **Delete Analysis**.
3. Make sure you do not have the "**Delete this project also?**" box checked. This will delete your history and is not reversible. Click **Delete Analysis**.
4. Now, use the **Attach Analysis Project** button at the top right of the screen to add the link.
5. You will now see a new popup window. Select the required option from the options given.
6. Rerun the request.
### Why am I getting an 'inactive user' error message?
Sometimes, an "**Inactive user**" error may appear at the start of an analysis:
This could be caused because the user who created the project and provided credentials for it:
* Is no longer a member of the team and was removed.
* Had their permissions changed in CodeScan.
* Had their permissions changed in the repo/environment that is scanned.
To resolve the “**Inactive user**“ issue, you need to reattach the project—without deleting its history.
Follow these steps:
1. Delete the project analysis:
**Important!** Do **not** select the checkbox to '**Delete Project also?'** if you want to keep the current project and its history:
2. Reattach analysis:
3. Provide repo/environment credentials:
4. Rerun the SCA; it should succeed.
If the steps above were completed but the issue persists, contact .
### Why am I getting an 'ip restricted' message?
The **IP restricted** issue can be solved by relaxing the IP restrictions for the CodeScan connected app in the org you are trying to scan.
To do this follow the below steps:
1. Log in to the org you are trying to scan.
2. Go to **Setup** and search for **Connected Apps OAuth Usage**.
3. Install the app that is making the scan (*CodeScan Cloud* or *CodeScan Quick Reports*).
4. Click **Manage App Policies** and then **Edit Policies**.
5. Under **IP Relaxation** select **Relax IP Restrictions**.
6. Rerun the scan.
### Why am I getting an error message: 'Job took too long after 1 hour of analysis'?
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:
1. Click **Project Settings > General Settings** in your Project Overview.
2. Click the **CodeScan** tab on the left and modify the timeout under the **Unit Test Timeout** once you're in **General Settings**.
### Why am I getting a 'Packfile is truncated' error?
While analyzing the project, you may encounter a “Packfile is truncated” error. Initially, access to CodeScan was denied on GitHub.
1. **Check Access:** Verify if you have the necessary access to CodeScan in GitHub.
2. **Grant Access:** If access is denied, request and obtain the required permissions for CodeScan.
3. **Retry Analysis:** After granting access to CodeScan in GitHub and integrating it with CodeScan, start the connection, then reattempt the project analysis. The error should no longer appear. The repositories should be synced. CodeScan should indicate the analysis was triggered, and the user should see the issues.
### Why am I getting the error: 'Project reports are not available for branches created outside the CodeScan Cloud'?
Error Message
For branches created outside the CodeScan Cloud, such as ARM, Flosum, or Copado, project reports are not yet accessible. Only the branch chosen during the initial integration setup with CodeScan Cloud can have reports fetched in CodeScan.
In the **Edit Project** section, select **“Attach Analysis Project,”** and choose the project type as **“Webhook.”**
Project Analysis page
After this step, project reports will be accessible.
Project Report page
### Why am I getting the error: 'Salesforce returned an unexpected result'?
The Salesforce Enhanced Domains feature was rolled out to Sandboxes on August 26, 2022, and available on September 9 for all environments.
If your CodeScan Cloud Salesforce project was linked to a Sandbox or Org that this feature is enabled in, you will need to reattach your project analysis.
[CodeScan Cloud](https://www.codescan.io/products/cloud/) allows you to do this *without erasing* the historical data present in your project.
To fix the above errors, first you need to delete the **Analysis Project**, to delete follow the steps below:
1. Go to your **Project** and navigate to the **Project Settings > Project Analysis** page.
CodeScan screenshot
2. Click on **Delete Analysis**.
Delete Analysis screenshot
3. Make sure you do not have the "**Delete this project also?**" box checked. This will delete your history and is not reversible. Click **Delete Analysis**.
Delete Analysis project checkbox
4. Now use the **Attach Analysis Project** button at the top right of the screen to re-add the link.
Attach Analysis Project
5. Configure the project and run the analysis.
### Why am I getting a unit test timeout?
In CodeScan Cloud, the default setting for unit test timeouts is 1 hour (3,600 seconds). For Orgs and Sandboxes with a large number of tests, this can be insufficient. To increase the timeout, click on your project and then navigate to **Overview > Project Settings > General settings**.
In General Settings, click on the **CodeScan** tab on the left and edit the timeout under the **Unit Test timeout**.
