Prerequisites

Maestro is based on Studio Web. To find out what are the requirements for using Studio Web, see the Automation Suite System Requirements.

Use this checklist to verify your environment is ready for Maestro. It covers tenant enablement, user roles and app permissions, and Unattended licensing across tenant, machine template, and folder. Missing any item commonly results in pending jobs.

Orchestrator permissions

You need the following permissions in the Orchestrator folder where the Maestro process is published:

• Processes.view and Processes.edit — to view or edit Maestro processes.
• Jobs.view and Jobs.edit — to view or edit process instances (jobs). You can grant equivalent permissions at the folder level. For more detauls, check Default roles and permissions.

Execution settings

For a process invoked from Maestro, manage its execution settings through Package Requirements in the deployed Agentic process. Check Linking execution settings.

Unattended runtime setup

While Maestro itself does not require allocating a runtime, jobs started by a Maestro process may require Unattended runtimes. For RPA workflows invoked via Maestro:

• At least one user or Robot account is enabled for Unattended, assigned to the tenant, and added to the target folder. Read Unattended robot setup for configuration steps, Robot accounts for service accounts, and Managing robots for folder assignment.
• Your folder has a machine template with a runtime assigned. Check Machine templates.