- 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
Common installation and configuration errors
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.
You may encounter this error while trying to install Autopilot, even with a stable network connection.
Clear your cache, and retry the installation.
Autopilot for everyone installation completes in three to five minutes, you need to keep the screen active until it finishes.
-
Go to Automation Ops > Solutions Management > Deployments.
-
Delete the Autopilot solution in the draft state.
-
Reattempt to install Autopilot from the AI trust layer tab.
Check tenant permissions for the user and ensure that the corresponding Enable user to run automations option is selected:
-
In Orchestrator, go to Tenant > Manage Access > Assign Roles > User.
-
Select the user.
-
In the Personal automations setup tab, select the Enable user to run automations option.
-
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.
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:
-
In Orchestrator, go to Tenant > Manage Access > Assign Roles > User.
-
Select the user.
-
In the Personal automations setup tab, select the Create a personal workspace for this user and enable optimal Studio Web experience option.
-
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.
-
Autopilot solution only comes with core processes (Autopilot, FAQ, Google, Wikipedia).
-
Download additional toolset automations from Marketplace.
-
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 folder is missing for selected tenant
- Failed to install Autopilot solution - Network error
- Autopilot does not install after leaving screen
- Autopilot installation fails with an error
- No robot configured for the current user
- Unable to see the Autopilot tab in Assistant
- Couldn't install widget
- ExternalHostShowTimeout error
- You need a personal workspace to use Autopilot
- Status code 424 - Unable to process uploaded PDF file
- No UiPath automations are available in Autopilot
- UiPath automation fails due to invalid connection issue
- Autopilot tab is stuck on loading screen