- À propos de ce guide
- Démarrage
- Installation en cours
- Mise à niveau
- Connecting and licensing
- Configuration
- Fichiers de configuration
- Rediriger les Robots vers un serveur proxy
- Configurer des dossiers de package et des chemins d’accès réseau
- Configurer des flux d’activité
- Configuration de la vérification de la signature des paquets
- Implémenter l’authentification avec le fournisseur d’informations d’identification
- Configurer l’exécution préchargée
- Running workloads
- RPA processes and tests
- Agents, functions, and API workflows
- Enabling agents, functions, and API workflows
- Executor packages
- Limits
- Securing and governing
- Surveillance
- Résolution des problèmes
- Résoudre les problèmes du service de robot UiPath
- Résoudre les problèmes d’exécution
- Unified Runtime troubleshooting
- Enregistrement et dépannage à distance
- Résoudre les problèmes de mise en réseau
- Résolution des problèmes de connexion
- Dépannage des licences
- Dépannage des packages
- Résolution des problèmes .NET
- Dépannage de la journalisation
- Dépannage des problèmes de session
- Référence (Reference)
Executor packages
Executor packages, the packages UiPath Robot 2026.10 restores to run agents, functions, and API workflows, and where the Robot gets them.
Executor packages are the parts of Unified Runtime that run agents, functions, and API workflows. RPA processes and test cases run in the .NET executor. The Robot installs executor packages the same way it installs the packages of a process, from a feed into the packages folder.
Which executor packages are available on a machine decides which of these workloads the robot reports to Orchestrator, and so which jobs Orchestrator sends it.
The executor packages
| Exécuteur (Executor) | Paquet (Package) | Exécutions |
|---|---|---|
| Python executor | UiPath.GenericExecutors.RobotAdapter.PythonCoded | Low-code agents, coded agents, and Python functions |
| JavaScript executor | UiPath.GenericExecutors.RobotAdapter.JsApi | JavaScript functions and API workflows |
| Executors host | UiPath.GenericExecutors.ExecutorsHost.Runtime | The host process the other executor packages run in. It runs no workload of its own. |
Jobs for the same executor package, user, and settings share one host process on the machine. In service mode, a job that runs as its own user gets a host for that user instead of sharing one with other users' jobs.
Where the Robot gets them
The executor packages ship with the Robot. The installer places them in the Executors folder of the Robot installation folder, and that folder is the Executors feed. The Robot doesn't download executor packages from the internet, so you don't need to allow a network endpoint or configure a feed for them.
When the Robot service starts, it reads the index of the Executors feed to find out which workloads the executor packages run, and reports them to Orchestrator. A job doesn't need to have run before for the robot to report a workload.
Versions and cache
Each Robot version ships with a fixed version of each executor package. Executor packages change only when the Robot is updated. For how updates reach the Robot, refer to Updating the Robot.
The Robot installs executor packages into the same packages folder as process packages. That folder is set by PackagesInstallationFolder in the UiPath.config file, and is %UserProfile%\.nuget\packages by default. For the packages folder, refer to Setting up package folders and network paths.
Offline machines
The executor packages are on the machine after installation. The language runtimes they need, such as Python, aren't part of the Windows installation. The executor packages get them the first time they run a job.
On a machine without internet access, the executor packages can't download these runtimes, so agent, function, and API workflow jobs can't get them. Make the runtimes available to the executors before you run these workloads on that machine.