Subscribe

UiPath Robot

The UiPath Robot Guide

About Automation Projects on the Robot

The Robot is an execution agent, meaning that you have to provide it with the automation projects you want it to run.

After creating an automation project in Studio, it needs to be published locally or to Orchestrator. Once a project is published, you can send it to the Robot machine and start executing it.

On the Robot machine, the automation packages feed is provided as the value of the NuGetServerUrl parameter, in the UiPath.Settings file (%ProgramData%\UiPath). This is populated by default as follows:

  • When NOT connected to Orchestrator - %ProgramData%\UiPath\Packages
  • When connected to Orchestrator - the default Orchestrator feed (~/NuGetPackages)
    Please note that these values can be customized to suit your needs.

Automation Projects when Connected to Orchestrator

While connected to Orchestrator, the UiPath Robot tray displays all the automation projects the given Robot has been associated with.

Robots that are connected to Orchestrator still need to download and unzip the automation packages locally to execute them. Consequently, when you deploy a package to an environment (create a process) in Orchestrator, it is automatically installed on all the Robot machines from the indicated environment, in the %ProgramData%\UiPath\Processes folder.

If for some reason an automation project is no longer available locally, it is marked with the update update_processupdate_process icon in the UiPath Robot tray. When you click this button, the package is downloaded and unzipped in the %ProgramData%\UiPath\Projects folder.

📘

Note:

The %ProgramData%\UiPath\Projects folder is automatically created when you first deploy a package to an environment (create a process) in Orchestrator.

If the automation project is not available locally when you start a job in Orchestrator, it automatically downloads it in the %ProgramData%\UiPath\Projects folder and all other dependencies (activities), and then starts the execution.

Automation Projects when Not Connected to Orchestrator

The UiPath Robot tray displays, in the Available Processes section, the automation projects that are stored as follows:

  • in both the %ProgramData%\UiPath\Packages and %ProgramData%\UiPath\Projects folders
  • only in the %ProgramData%\UiPath\Packages directory. These items are marked with the update update_processupdate_process icon. Clicking this button unzips the process in the %ProgramData%\UiPath\Projects folder.

Only automation projects that are present in the %ProgramData%\UiPath\Packages folder and decompressed in the %ProgramData%\UiPath\Projects folder can be executed directly.

📘

Note:

The %ProgramData%\UiPath\Packages folder is created when you first publish an automation project from Studio. If you are not connected to either Studio nor Orchestrator, you have to create this folder.
The %ProgramData%\UiPath\Projects directory is created when you decompress the first automation package.

Updated about a year ago



About Automation Projects on the Robot


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.