UiPath Documentation
maestro
latest
false
UiPath logo, featuring letters U and I in white

Maestro user guide

Last updated Mar 13, 2026

Publishing and upgrading agentic processes

Note:

Make sure all validation errors are fixed before publishing your Maestro process.

Choose the default entry point​

If you have multiple start events, you need to choose your default entry point.

  1. In UiPath Orchestrator, go to Automations → Processes (Agentic processes).
  2. Select the process.
  3. From the three dots menu, select Edit.
  4. In the Runtime arguments field, select a default entry point from the drop-down list.
  5. Choose Update.

See the Orchestrator user guide for more details about entry points.

Publishing agentic process projects​

You agentic process is part of a solution. Read about solutions in the Studio Web user guide. To publish an agentic process project:

  1. Select the Publish button at the top of the process canvas.
  2. In the Publish solution window, enter a name and a changelog for your process, and select a version.
  3. Select Publish.

You can then access your published process after deploying it to Orchestrator. Read Publishing and deploying solutions for the steps to publish to Orchestrator.

publish automations

Note:

Agentic processes published to the Orchestrator Personal Workspace feed are automatically deployed to Orchestrator, and you can run them immediately.

Note:

If the agentic process requires execution on a UiPath Robot, ensure that a robot account is available and configured. For setup instructions, see Managing accounts and local groups.

Roles and permissions​

To publish to a tenant feed, you need one of the following:

  • The Packages - Create permission
  • The Allow to be Automation Publisher role

To publish to a folder feed, you need one of the following:

  • The Packages - Create permission
  • The Automation Publisher role

Configuring execution identity for child processes​

When an agentic process invokes child processes — such as RPA workflows or agents — each child runs as an Orchestrator job that requires an execution identity (a robot account and machine). By default, if no identity is explicitly configured, the child process runs under any available account assigned to the folder where it is deployed.

For scenarios where parent and child processes must operate under different levels of access, you have two options:

Option 1: Folder-based isolation​

Deploy the parent Maestro process and each child process in separate Orchestrator folders, each with its own identity assignments. By default, each process runs under any available identity in its own folder. You can further control this using account-machine mappings within each folder.

Use this approach when your team manages access at the folder level and wants a clear organizational separation between the parent orchestration logic and child automations.

Option 2: Explicit execution settings via Package Requirements​

You can explicitly configure the account and machine for each child process invoked by the parent. You can perform this configuration in Orchestrator after deploying your Maestro process:

  1. In Orchestrator, go to Automations, then to Processes.
  2. Select your agentic process.
  3. Go to the Package Requirements tab.
  4. Find the child process (type: Process or Agent) in the requirements list.
  5. Select Execution settings next to that process.
  6. Configure:
    • Runtime type — the type of runtime to use.
    • Account — select a specific robot account, or choose Run as myself to run the child process under the same identity as the parent.
    • Machine — select a machine or machine template.
  7. Save the configuration.

Configured entries are marked with a blue indicator on the Update execution settings button.

For full details, read Managing Package Requirements – Linking execution settings in the Orchestrator documentation.

Tip:

Use Option 2 for fine-grained, per-child-process identity control within a single folder. Use Option 1 when you prefer to manage access at the folder level and want a clear organizational boundary between parent and child processes.

Note:

The Run as myself option under Account forces the child process to run under the same identity as the Maestro parent process. This is useful when you want consistent identity propagation across the entire execution chain.

Publishing and deploying solutions​

For more advanced automation scenarios that involve multiple projects packaged together, consider using solutions. Solutions allow you to publish and deploy full automation suites—including agentic and non-agentic projects—as a unified package. Learn more about Publishing and deploying solutions.

Upgrading agentic process projects​

When you publish a new version of an agentic process, an Updates are available icon appears under the Version column in Orchestrator. To upgrade your published project:

  1. Select the button on the right of the process.

  2. Select Upgrade to latest version.

    upgrade to latest version

  3. Select the Confirm button in the Update package version window.

    update package version

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated