# Automation Anywhere Troubleshooting

If you encounter any of the following issues or errors while configuring the Automation Anywhere 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.
2. Check for typos in the hostname.
3. Confirm the Automation Anywhere Control Room tenant is active (not suspended).

## Authentication failed: token missing from response

**Cause**: Automation Anywhere username or password is incorrect or the account is locked

**Resolution**:

1. Verify the Automation Anywhere username and password configured in SailPoint:

   1. Go to Automation Anywhere **Control Room \> Administration \> Users**.
   2. Confirm the user account exists and is active.
   3. Reset the password if needed and update the connector configuration.
2. Confirm the user account is not locked or disabled in Automation Anywhere Control Room.
3. Ensure the Automation Anywhere Control Room URL (`Base URL`) points to the correct tenant.
4. Verify that the user has API access enabled in Automation Anywhere Control Room.

## Automation Anywhere token validation failed: token is not valid

**Cause**: The token obtained during authentication failed the validation step

**Resolution**:

1. Verify the Automation Anywhere Control Room URL is correct and reachable.
2. Confirm the Automation Anywhere user account has not been deactivated between authentication and validation.
3. Check that the Automation Anywhere Control Room version supports the `/v1/authentication/token` validation endpoint.
4. Try re-running Test Connection; a transient Control Room issue may cause intermittent token validation failures.

## Connection test failed: 401 Unauthorized

**Cause**: Automation Anywhere credentials are invalid or the user account lacks API access

**Resolution**:

1. Verify the Automation Anywhere username and password in the connector configuration.
2. Confirm the user account exists and is not locked in Automation Anywhere Control Room:

   1. Go to Automation Anywhere **Control Room** \> **Administration** \> **Users**.
   2. Check the account status.
3. Ensure the user has the **AAE\_Basic** role or equivalent that allows API authentication.
4. Verify that the Automation Anywhere Control Room URL (`Base URL`) is correct and does not include a trailing slash.

## Bot file ID not configured; required for operation

**Cause**: The bot file ID for the requested operation is missing from the connector configuration

**Resolution**:

1. Verify that the bot file ID is configured in SailPoint for the required operation:

   1. Create `FileId`
   2. Update `FileId`
   3. Delete `FileId`
   4. Enable `FileId`
   5. Disable `FileId`
2. To find the correct file ID in Automation Anywhere Control Room:

   1. Log into Automation Anywhere Control Room.
   2. Go to **Automation \> Bots**.
   3. Find your bot.
   4. The file ID is the numeric ID shown in the bot details or in the URL.
   5. Copy the numeric ID and paste it into the SailPoint configuration.
3. Ensure the bot is uploaded and available in Automation Anywhere Control Room (not just locally saved).
4. Verify that the Run As User (`aaRunAsUserIds`) has permission to run the bot.

## Bot execution FAILED or Bot execution STOPPED

**Cause**: The Automation Anywhere bot encountered an error during execution or was manually stopped

**Resolution**:

1. Log into Automation Anywhere Control Room and check the activity logs:

   1. Go to **Activity \> Historical**.
   2. Find the failed or stopped activity.
   3. Review the error details and bot execution logs.
2. Common causes:

   1. Target system is unavailable or credentials used by the bot have expired.
   2. Bot logic encountered an unexpected UI or API response in the target system.
   3. Bot was manually stopped by a Control Room administrator.
3. Verify that the Run As User device or bot runner is online and available.
4. If using device pools (`poolIds`), confirm at least one device in the pool is active.
5. Re-run the provisioning request after resolving the underlying bot error.

## Bot output Status is false

**Cause**: The bot completed successfully in Automation Anywhere Control Room but the operation failed in the target system

**Resolution**:

1. Check the `message` output variable returned by the bot for details about the failure.
2. Common causes:

   1. Account not found in target system (for UPDATE, DELETE, ENABLE, DISABLE).
   2. Duplicate account detected (for CREATE).
   3. Target system returned a validation error, like invalid attribute value
3. Review the bot execution logs in Automation Anywhere Control Room for more detail:

   1. Go to **Activity \> Historical**.
   2. Find the completed activity.
   3. Check bot log output for the specific error.
4. Correct the underlying data issue and re-run the provisioning request.

## aaRunAsUserIds is required but not configured

**Cause**: No Run As User ID is configured in the connector provisioning settings

**Resolution**:

1. Configure at least one Run As User ID in the connector configuration (`aaRunAsUserIds`).
2. To find the Run As User ID in Automation Anywhere Control Room:

   1. Go to **Administration \> Users**.
   2. Find the user that the bot should run as.
   3. The user ID is the numeric ID shown in the user details or in the URL.
   4. Copy the numeric ID and paste it into the SailPoint configuration.
3. Verify that the Run As User has an active device or is assigned to a device pool.
4. Ensure the Run As User has permission to execute the configured bots.