How to handle when processes are not showing up in the Robot Tray?
Issue Overview: Processes are not showing up in the Robot Tray. Alternatively, the process show-up in the Robot tray intermittently.
For Classic folders.
- Make sure that the Robot is a part of the same environment that the processes are associated with.
- Login to Orchestrator and make sure that the processes are visible in the process page and not showing any errors. Also make sure each package is visible in Orchestrator. It could be this is an Orchestrator issue. If any problem is found, try searching for that issue in our KB article database.
- If Orchestrator is multi-node and the Robot and processes are part of the same environment do the following
- Login to the Orchestrator server
- Open the web.config file in the Orchestrator installation directory
- Check to see what type of storage mechanism is being used. Search for Nuget.Repository.
- If it says “Legacy”, search for “Nuget.Repository.Path” to find the location where packages are being stored.
- If it says “Composite”, search for “Storage.Location” to find where packages are being stored.
- Login to each Orchestrator instance to validate that all instances are sharing the same storage location. (i.e. a shared network drive, or a storage service like S3 or Azure blobs.)
- If they are not, see the section labeled Fixing Orchestrator Storage.
- If the storage location is the issue, as a workaround, try having the users connect directly to one of the Orchestrator instances.
- If the issue continues, please check the event viewer logs of Orchestrator and the Robot Machine for errors that indicate the problem. If nothing is found, please open a ticket with UiPath and include the web.config of Orchestrator.
Fixing Orchestrator Storage
For Multi-node deployments, Orchestrator should use a shared location for storage. For details on specific configurations see Web.Config .
If using a shared network drive for storing the packages, make sure that each Orchestrator instances has access to the drive.
- Open IIS and go to the “Application Pools” section.
- Check to see what user identity is being used to execute the UiPath Orchestrator application pool.
- The user running the application pool needs to have permissions to access the network drive.
- If the application pool is using the built-in app pool identity (which is best practice) there will not be an user account to add to the Network Drive. Instead the computer needs to be granted permissions to the network drive.
- Built in App Pools just use the computers credentials to access network resources.
- The user to add in the permissions window is <computerName>$ (i.e. MyComputer$)
- Read more on the Application Pool Identities .