- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-library-object-repository
- get-object-repository
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- pack
- publish
- remote
- restore
- run, debug & execution
- run-file
- search-templates
- start-studio
- stop-execution
- tm
- uia
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
uip maestro bpmn validate
Syntax and options for `uip maestro bpmn validate`, which structurally validates a single .bpmn or Studio Web XML export file.
uip maestro bpmn validate validates a single .bpmn file (or a Studio Web BPMN XML export) for structural correctness — well-formed BPMN plus UiPath extensions — without touching any project metadata files. It's registered under the bpmn branch.
Synopsis
uip maestro bpmn validate <file>
uip maestro bpmn validate <file>
Honors global options. Exit codes follow the standard contract.
Arguments
<file>(required) — path to the.bpmnor.xmlfile to validate. This is a single file, not a project directory.
Examples
uip maestro bpmn validate process.bpmn
uip maestro bpmn validate export.xml
uip maestro bpmn validate process.bpmn
uip maestro bpmn validate export.xml
Data shape (--output json)
{
"Code": "BpmnValidate",
"Data": {
"File": "process.bpmn",
"Status": "Valid",
"ProcessCount": 1,
"StartEventCount": 1,
"UiPathExtensionCount": 4
}
}
{
"Code": "BpmnValidate",
"Data": {
"File": "process.bpmn",
"Status": "Valid",
"ProcessCount": 1,
"StartEventCount": 1,
"UiPathExtensionCount": 4
}
}
When the file is valid but has warnings, Data also carries Warnings: the warning count followed by one line per warning.
When validation fails, the command exits with code 1 and returns Result: "Failure" with Message: "Validation failed for <file>". Instructions holds the error count followed by one line per issue, with the element path, the rule code, the message, and the fix when one is known.
Checks
The command checks the BPMN XML, the UiPath extensions, and the rules the Maestro canvas applies. These checks include:
| Rule code | Severity | Fires when |
|---|---|---|
MISSING_DI_SHAPE | error | A flow node has no bpmndi:BPMNShape in the diagram. Run uip maestro bpmn format to regenerate the layout. |
MISSING_DI_EDGE | error | A sequence flow has no bpmndi:BPMNEdge in the diagram. Run uip maestro bpmn format to regenerate the layout. |
MISSING_BINDING | error or warning | A binding doesn't match a resource in the tenant: a connection, a release, or an action app. The fix line explains how to find the matching resource. |
PLATFORM_BINDINGS_UNVERIFIED | warning | The binding checks against the tenant couldn't complete, so the affected bindings weren't verified. Check uip login status, the selected tenant, and the network connection, then run validate again. |
An unsupported UiPath extension type is reported as a warning. uip maestro bpmn pack treats it as an error.
See also
uip maestro bpmn init— scaffold a new project with a valid starter BPMNuip maestro bpmn refresh— regenerate project metadata from a validated.bpmnuip maestro bpmn pack— pack a project for deployment- Maestro overview