Maestro user guide

The process overview homepage provides an operational summary of all processes instances, and includes an active instances dashboard, a table of all incidents, and a table of all processes.

The active instances dashboard displays the count of all instances, broken down by running vs. faulted instances.

The incidents table displays all unresolved incidents, with each incident corresponding to a faulted instance. The table is organized by error message per process and includes the time elapsed since a specific error message was first seen for that process.

The processes table contains a list of all processes in the tenant that the user has access to. The table includes the counts for the number of running instances, faulted instances, and total instances, as well as the number of versions and the folder location in Orchestrator.

When you select a specific process from the Processes table, a table of all instances for that process appears. Additionally, you can view a diagram representing the process model by selecting a single version in the table.

The all process instances dashboard offers a real-time and historical view of every process execution across your workspace. Use this screen to monitor automation activity, troubleshoot failures, and understand performance trends.

When you select a single instance from the All instances view, a diagram showing the execution status of each step appears. This diagram is accompanied by the instance execution trail and pertinent variable and action history data. The single instance view allows you to see the entire execution trail, action history, step details, and global variables in one centralized location.

The instance execution trail clearly delineates each step in the instance process’s execution, including hierarchical steps such as agents and subprocesses. To further investigate, you can select a specific node on the diagram or a step in the Execution trail. The selected component will be highlighted in blue, revealing details such as step ID, label, input/output variables, execution duration, and links to additional tasks, such as opening a job or app task.

The Action history tab displays details for instance management actions that have been taken,including details about the action performed, the individual responsible, and any comments provided. This exhaustive information ensures complete transparency and traceability of each step in the instance execution.

In the Execution trail tab, if you click the first row, you will display the Global variables, but if you click any other row you will trigger the display of the Variables.

The processes in this view are based on the permissions you have as a user in Orchestrator, more specifically:

You can also manage the instance, including pause, resume, retry, cancel, move, and migrate. When you perform one of these actions, there is a comment section where you can log additional details. These comments are then shown in the action history section.

Pause

Performing the pause action on an instance pauses the execution after all currently running steps have completed.

Resume

Performing resume on an instance will resume the execution.

Retry

Performing the retry action on an instance restarts all the current activities in the workflow from the last completed step. Typically this is done after editing a variable or updating something in an external system for a faulted instance.

Migrate

Performing the migrate action on an instance upgrades it to a different version of the process. This allows you to update the instance with the latest logic and configurations from the target version.

Cancel

Performing the cancel action on an instance will stop all current activities and terminate their progress in the agentic process. This action is irreversible.

Move

Executing the Move action on an instance enables you to alter the sequence by relocating the execution to a different process element. This is typically applied to faulted or paused instances when a prior step requires re-execution or when you want to bypass the current steps and proceed to later ones.

After performing the move, you must select either the Retry or Migrate option to resume execution.

This page explains how Maestro supports auditability, operational traceability, and compliance for long-running, multi-actor processes. It describes what execution data Maestro records, why that data is recorded, where you can access it, and how you can retain or export it to meet regulatory and operational requirements.

This information applies to processes orchestrated by Maestro in UiPath Automation Cloud. Maestro relies on core UiPath platform services (such as Orchestrator, Automation Cloud audit logging, Insights, and the AI Trust Layer) to enforce logging, retention, and access controls.

Maestro logging is designed to support the following outcomes:

Maestro records orchestration-level execution metadata rather than full business payloads. This design balances auditability, performance, and data-minimization requirements.

For each process instance, Maestro records execution metadata that describes what ran, when it ran, and who or what executed it.

Maestro records:

Maestro records this data to support operational monitoring, troubleshooting, and audit reconstruction of process behavior.

Maestro records execution identity information that allows you to determine who or what performed each step.

For each executed step, Maestro records:

Maestro does not store a dedicated actor-type field such as human, robot, or agent. You can infer the actor type from the recorded identity and execution context.

This approach preserves traceability without duplicating identity models across platform services.

Maestro records execution paths rather than abstract decision labels.

Maestro does not record explicit decision or rule-outcome fields. Instead, Maestro records the path taken through gateways, subprocesses, and conditional flows.

You can reconstruct decisions by reviewing:

This design allows auditors and operators to understand why a process followed a specific route without introducing redundant decision artifacts.

Maestro limits data persistence to reduce exposure of sensitive information.

By default, Maestro does not record:

Maestro records variable state snapshots at step completion to support traceability and debugging.

When a process uses files, Maestro handles them as job attachments that are scoped to a single process instance. Platform permissions and retention policies control access to these files.

UiPath surfaces Maestro execution data through multiple operational and audit views.

You can use:

Insights ingests Maestro execution events, including process runs, element runs, and incidents. UiPath exposes this data through the Maestro template dashboard, which supports audit reviews, operational reporting, and trend analysis.

Together, these views support drill-down analysis from high-level monitoring to individual execution steps.

UiPath Automation Cloud manages audit logging and retention for Maestro executions.

By default:

Retention periods depend on platform tier and service configuration. You can export audit and Insights data to meet longer retention or regulatory requirements.

You can export Maestro-related audit logs and execution metadata to support compliance, investigations, and long-term archiving. UiPath supports CSV export of audit logs from Automation Cloud. You can store exported data in customer-managed systems or ingest it into governance, risk, and compliance workflows.

When a process uses AI-powered steps routed through the AI Trust Layer, UiPath records audit metadata about AI usage.

This metadata includes:

By default, UiPath excludes customer prompts and AI-generated content from audit logs. You can configure AI governance policies to control logging behavior where required.

Availability of AI audit details depends on feature configuration and release status.

You can correlate Maestro execution data with logs from external systems such as Salesforce, ServiceNow, or AWS.

To support end-to-end traceability, you can use:

You can export Maestro audit data and ingest it into customer-managed logging or SIEM platforms to support centralized monitoring and audit workflows.

Maestro follows data-minimization principles and avoids persisting unnecessary information.

By default, Maestro does not record:

This design supports secure operations while preserving the ability to reconstruct process execution behavior for audit and compliance purposes.