# UiPath Troubleshooting

If you encounter any of the following issues or errors while configuring the UiPath RPA platform, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## Connection test failed: Unknown host

**Cause**: Base URL is incorrect or network cannot resolve hostname

**Resolution**:

1. Verify the base URL format:

   - Correct - `https://cloud.uipath.com/mycompany`
   - Incorrect - `https://cloud.uipath.com/mycompany/orchestrator_/`
2. Check for typos in the hostname.
3. Verify DNS resolution (ping the hostname).
4. Check that the firewall allows outbound HTTPS (port 443).
5. Confirm the UiPath tenant is active (not suspended).

## Connection test failed: 401 Unauthorized

**Cause**: API token is invalid, expired, or incorrect

**Resolution**:

1. Generate a new API token in UiPath:

   1. Go to **UiPath Admin \> API Access**.
   2. Create a new personal access token.
   3. Copy the token immediately, as it cannot be viewed again.
2. Paste the new token into SailPoint configuration.
3. Verify the token hasn't expired (check expiration date in UiPath).
4. Ensure the token is for the correct tenant or folder.
5. Verify that the service account has API access permissions.

## Connection test failed: 403 Forbidden

**Cause**: API token lacks required permissions

**Resolution**:

1. Check token permissions in UiPath:

   - Must have the **View** permission on Orchestrator.
   - Must have the **Execute** permission for jobs.
   - Must have the **Read** permission on Data Fabric, if you're using API aggregation.
2. Use an account with Administrator role (for testing).
3. Review the organizational unit permissions.
4. Ensure that the token is not restricted to specific folders.

## Connection test failed: 404 Not Found

**Cause**: Incorrect Organization Unit ID or base URL

**Resolution**:

1. Verify the Organization Unit ID:

   1. Log into UiPath Orchestrator.
   2. Go to the target folder.
   3. Check URL for the `fid=` parameter. This is your Organization Unit ID. For example in `.../folders?fid=123456`, the Organization Unit ID is `123456`.
2. Verify the base URL doesn't include the `/orchestrator_` or `/dataservice_` service paths.
3. Confirm that the folder exists and is accessible to API token.

## No records returned from aggregation

**Cause**: Empty data source or incorrect configuration

**Resolution**:

**For Data Fabric** (UiPath)

1. Verify the Data Fabric entity has records:

   1. Log into the UiPath Data Service.
   2. Query the entity manually.
   3. Confirm that the records exist.
2. Check that `dataFabricEntityId` matches entity name exactly.
3. Verify that the API token has read permission on the entity.
4. Check that the Organization Unit ID is correct.

**For SFTP**

1. Verify that the CSV file exists at the specified path.
2. Check that the file contains data rows, not just headers.
3. Verify that the file format is correct; a proper CSV with header row.
4. Confirm that the SFTP user can read the file.

## Aggregation times out

**Cause**: Large dataset or slow network

**Resolution**:

1. Check record count:

   1. **Data Fabric**: Query entity, check the `totalRecordCount` attribute.
   2. **SFTP**: Check the CSV file size/row count.
2. If \>10,000 records:

   1. Expect one to two hours for aggregation duration.
   2. Increase timeout settings in SailPoint (if configurable).
   3. Consider scheduling during off-peak hours.
3. Optimize the data source:

   1. Remove unused attributes (fewer columns).
   2. Filter out inactive accounts (if possible).
4. Check network speed between SailPoint and the SFTP server.

## Release key not found

**Cause**: The release key is incorrect or the workflow is not deployed

**Resolution**:

1. Verify that the release key in SailPoint matches the one in UiPath:

   1. Log into UiPath Orchestrator.
   2. Go to **Processes**.
   3. Find your workflow.
   4. Select **Workflow \> View details**.
   5. Copy the **Key** field value.
   6. Paste it into the SailPoint configuration.
2. Ensure the workflow is deployed, not just published. The workflow must be in **Processes**, not just in **Packages**.
3. Check that the workflow is in the correct folder or organizational unit.
4. Verify that the API token has execute permissions on the workflow.