UiPath Launches Maestro Case to Manage Exception-Heavy Workflows

UiPath on June 16, 2026, launched Maestro Case, an AI-native case management capability designed to coordinate AI agents, robots, people, applications, and data across complex, long-running enterprise processes.

The product extends UiPath’s Maestro orchestration suite — which already handles structured Business Process Model and Notation (BPMN) workflow automation — into dynamic, unstructured work where the next step cannot be determined at design time.

Built for Work That Doesn’t Follow a Script

Maestro Case addresses a structural limitation in conventional workflow automation: BPMN-based process models require a fixed sequence defined before execution begins, a design that breaks down when incoming information changes the path.

KYC investigations, insurance claims, and loan underwriting files do not follow fixed scripts — each accumulates data, participants, rules, and history as it moves toward resolution. Maestro Case treats that evolving record as the primary work object, carrying its context across every stage, actor, and connected system.

The product is built around three operational surfaces. The Case Plan Designer is where architects and developers model stages, task types, SLAs, and escalation rules. Case Instance Management gives operations teams runtime controls over live cases. The Case App gives case workers and managers a built-in workspace for case lists, task inboxes, and detail views — available out of the box or extensible through a pro-code TypeScript SDK.

The Case Manager applies deterministic CMMN-based rules first, invoking AI agent reasoning only when no rule covers the situation. Cases run through stages and tasks, with ten task types and three execution modes: Sequential, Event-driven, and Ad-hoc.

Where Exceptions Are the Business Model 

A financial services firm running dispute resolution and KYC workflows reported projected annual savings of more than $12 million after deploying Maestro Case. The result comes from processes that share a common profile: long duration, multiple handoffs across teams, and regulatory requirements that demand a documented decision trail.

The loan approval process helps illustrates the pattern. A mortgage application moves through credit review, compliance checks, and underwriting — each stage conditional on the last, each requiring a different team, and each capable of stalling on an exception.

Dispute resolution and KYC remediation work the same way, as do vendor onboarding, insurance claims, and order fulfillment exceptions. These are processes where the path changes based on what each review finds, not a sequence that can be scripted in advance.

Maestro Case connects to the systems already running these workflows. It accepts upstream identifiers — an ERP order ID, a CRM case number, a policy number — so active cases draw on data resident in ERP, HRIS, and ITSM systems without migration.

SLA tracking runs at the case, stage, and task level, with escalation rules that fire automatically when deadlines are at risk. Access is governed by stage-aware personas, meaning a case worker’s permissions reflect where the case currently stands.

“Modern case management is no longer about tracking work — it’s about orchestrating dynamic complex processes, where exceptions are the norm,” said Raghu Malpani, Chief Technology & Product Officer at UiPath.

Entering a Crowded Market With a Different Approach

Maestro Case does not arrive in a vacuum. UiPath’s February 2026 acquisition of WorkFusion brought domain-trained KYC and AML agents into the platform — agents already deployed at Scotiabank and Deutsche Bank. Maestro Case give those agents a governed orchestration layer, connecting investigative workflows to a full case lifecycle.

Maestro Case enters a market with established incumbents. ServiceNow, Pega, and Appian built case management businesses around structured, platform-native workflows.

UiPath’s differentiation centers on architecture: Maestro Case is built around open standards and multi-vendor coordination as its primary design premise. It accepts agents and workflows from outside the UiPath platform, connects to ERP, CRM, and ITSM systems through native connectors, and uses MCP and A2A protocols to coordinate across AI platforms regardless of vendor.

SAP-centric organizations have a specific context for that positioning. SAP’s native process tools handle SAP-to-SAP workflows well. Maestro Case is designed for the exceptions that cross system boundaries — a dispute that starts in a CRM, touches an ERP record, requires a compliance review, and needs a single audit trail across all three.

What This Means for SAPinsiders

• Exception-heavy processes need a dedicated orchestration layer. UiPath built Maestro Case specifically for work that cannot be scripted in advance — KYC investigations, dispute resolution, vendor onboarding — where the next step depends on what the current step finds. Enterprises running those processes across disconnected systems now have a single governed layer to coordinate them.
• Regulated industries have the clearest immediate use case. Financial services, insurance, and healthcare share the same operational profile Maestro Case is designed for: high exception rates, strict audit requirements, and multi-party coordination across long-running workflows. Organizations in those sectors with active automation programs have the most direct path to deployment.
• SAP environments have a specific entry point for Maestro Case. SAP’s native process tools handle SAP-to-SAP workflows well. Maestro Case is designed for the work that crosses system boundaries — disputes, escalations, and compliance reviews that touch ERP, CRM, and ITSM simultaneously and require a single audit trail across all three.