Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

Environments

An environment is a grouping of Robots that is used to deploy processes.

The Environments page displays all previously created environments and enables you to manage Robots within them.

📘

Important!

If you have multiple Robots on the same machine (such as User Mode Robots or Service Mode Robots), it is recommended that you group them in the same environment. Otherwise, some errors might occur when deploying different versions of the same process.

To access the Environments page, click the Environments tab in the Robots page.

Best Practices

Use meaningful names and descriptions for each environment created.

Orchestrator Environments should map the groups of process execution. Each environment should have a specific role in the company's business logic.

If a Robot is going to execute two different roles, it can be assigned to multiple environments. If you have multiple Robots on the same machine, it is recommended that you group them in the same environment. Otherwise, some errors might occur when deploying different versions of the same process.

Access management between Robots and processes is done by using Environments properly.

Assigning Packages to Environments


It is good practice to assign each package published to Orchestrator to an environment. The deployment decision is taken in the Processes page. All the Robots from the environment get access to the package version set for this process.

When a new version of a process is available, an icon informs the user.

Rolling back to the previous version is always an option if something goes wrong after updating. This can be done by pressing the Rollback button.

Updated 9 months ago



Environments


Suggested Edits are limited on API Reference Pages

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