UiPath Robot

The UiPath Robot Guide

About the Activities Feed



Process and activities packages are installed per-user starting with v2018.2. This means that HD Robots now use their own version of activities and no longer share them with the other Robots on that machine.

To have a specific automation project run by a Robot, firstly you need to provide it with access to the automation package and to the activities that make it up.

The activities feed of the Robot is stored in the ActivitiesFeed parameter of the UiPath.settings file, which can be found in the %ProgramData%\UiPath folder.

If during the installation process you chose to add a local activities feed, they are stored as archives in the C:\Program Files (x86)\UiPath\Studio\Packages directory. If you chose not to install the local activities feed, only the Core ones are available in the aforementioned folder.

Regardless of whether or not you installed a local feed when you connect the Robot to Orchestrator, it is automatically changed to Orchestrator's feed - ~/NuGetPackages/Activities. This value is customizable and kept on the Orchestrator machine, in the NuGet.Activities.Path parameter of the web.config file.



As of 2018.2, processes are installed per-user (%USERPROFILE%\.nuget\Packages), instead of machine-wide (%PROGRAMDATA%\UiPath\Projects).

When you give the execute command to the Robot (be it in the UiPath Robot tray or Orchestrator), it looks for all its dependencies (activities, automation projects) and retrieves them. Even if the activities feed is local or not, when it comes to activities, it unzips and installs all the required ones in the %LocalAppData%\UiPath\Activities directory.

If the indicated version of an activity pack does not exist, the Robot looks for and downloads a higher version from the source which responds the fastest.



The Activities directory is created automatically the first time you execute an automation project.

The C:\Program Files (x86)\UiPath\Studio\Packages directory also stores a configuration file called packages.config. It determines which packages are installed by default when Studio opens, if they exist in the activities feed, be it local or on Orchestrator. To edit this file you need administrator rights.

Updated 3 years ago

About the Activities Feed

Suggested Edits are limited on API Reference Pages

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