autopilot
latest
false
  • Managing Autopilot for everyone
  • Configuring Autopilot for everyone
  • Deploying the Admin App
  • Deploying toolset automations
  • Troubleshooting
    • Common installation and configuration errors
    • Autopilot for everyone FAQ
Autopilot for everyone - Admin Guide
Last updated Nov 6, 2024

Common installation and configuration errors

Autopilot folder is missing for selected tenant

You may encounter this error after having Autopilot installed in your tenant. This is because a different user installed Autopilot, therefore you might need access to the Autopilot folder.

Assign yourself to the Autopilot folder in the selected tenant.

Failed to install Autopilot solution - Network error

You may encounter this error while trying to install Autopilot, even with a stable network connection.

Clear your cache, and retry the installation.

Autopilot does not install after leaving screen

Autopilot for everyone installation completes in three to five minutes, you need to keep the screen active until it finishes.

Autopilot installation fails with an error

  1. Go to Automation Ops > Solutions Management > Deployments.

  2. Delete the Autopilot solution in the draft state.

  3. Reattempt to install Autopilot from the AI trust layer tab.

No robot configured for the current user

Check tenant permissions for the user and ensure that the corresponding Enable user to run automations option is selected:

  1. In Orchestrator, go to Tenant > Manage Access > Assign Roles > User.

  2. Select the user.

  3. In the Personal automations setup tab, select the Enable user to run automations option.

Unable to see the Autopilot tab in Assistant

  • Make sure you have a valid user license: Automation Developer, RPA Developer, Citizen Developer, Attended.

  • Make sure there is no active Assistant policy which disables the Autopilot widget.

Couldn't install widget

Upgrade your Assistant version to 2024.10.5 Enterprise edition.

ExternalHostShowTimeout error

Upgrade your Assistant version to 2024.10.5 Enterprise edition.

You need a personal workspace to use Autopilot

Check tenant permissions for the user and ensure that the corresponding Create a personal workspace for this user and enable optimal Studio Web experience option is selected:

  1. In Orchestrator, go to Tenant > Manage Access > Assign Roles > User.

  2. Select the user.

  3. In the Personal automations setup tab, select the Create a personal workspace for this user and enable optimal Studio Web experience option.

Status code 424 - Unable to process uploaded PDF file

  • Make sure Document Understanding is enabled for your tenant.

  • You must have at least 1 AI unit allocated to your organization before you can enable Document Understanding in any tenant.

  • Users are restricted from processing PDF files.

No UiPath automations are available in Autopilot

  • Autopilot solution only comes with core processes (Autopilot, FAQ, Google, Wikipedia).

  • Download additional toolset automations from Marketplace.

UiPath automation fails due to invalid connection issue

  • Restart Assistant.

  • Go to Integration Service > Personal Workspace:

    • Check the connection to ensure it is valid.

    • Remove the connection, recreate it, then restart Assistant.

Autopilot tab is stuck on loading screen

Restart the Assistant.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.