- 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 maestro authoring
- uip maestro registry
- uip model-hub
- activities find
- activities get-default-xaml
- analyze
- analyzer-rules list
- build
- cleanup
- data-fabric-entities install
- data-fabric-entities list
- files diff
- get-library-object-repository
- get-object-repository
- init
- instances list
- pack
- packages inspect
- packages install
- packages versions
- publish
- remote
- restore
- run, debug & execution
- settings
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- tm
- uia
- validate
- workflow-examples get
- workflow-examples list
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
uip maestro flow validate
Syntax and options for `uip maestro flow validate`, which validates a `.flow` file against the schema and optional governance policies.
uip maestro flow validate validates a .flow file against the Flow schema with structural cross-field checks. An optional --governance pass additionally validates agent nodes against your organization's governance policies.
Synopsis
uip maestro flow validate <flowFile> [--governance] [--strict-bindings] [--strict-expressions] [--force]
uip maestro flow validate <flowFile> [--governance] [--strict-bindings] [--strict-expressions] [--force]
Honors global options. Exit codes follow the standard contract.
Arguments
<flowFile>(required) — path to the.flowfile, or a project directory containing one. For a directory, the command validates the same.flowfile thatuip maestro flow debugruns: theMainFilefromproject.uiproj, then<Name>.flow, then the first.flowfile in the project root,content/, orflow_files/. The command fails when the directory has no.flowfile.
Options
--governance— also validate agent nodes against organization governance policies. Requiresuip login; the CLI fetchesenforcementsand the allowedmodelNamesfrom the platform before running the check. If the fetch fails, the command errors out — omit--governanceto skip policy checks.--strict-bindings— fail validation when a Managed HTTP node (core.action.http.v2) carries a connector-shaped label but no Integration Service binding. Default: warn only — omitting this flag still runs the check, it just doesn't fail the build.--strict-expressions— fail validation when an expression or script body has a type error, per the same expression checker the canvas uses. Default: warn only. This CI-gating check always runs; the flag only controls whether its findings are fatal.--force— refetch the current node manifests that the stale-handle check uses, instead of reading the cached copy. The cache is the oneuip maestro flow registry pullwrites, kept 30 minutes per tenant, and the refetched manifests replace it, asregistry pull --forcedoes.
Behavior
- Schema validation runs locally and does not require login.
- Structural checks ensure references between nodes, edges, bindings, variables, and definitions are consistent.
- The stale-handle check compares each edge handle with the current node manifests, in addition to the definitions embedded in the
.flowfile. Studio Web renders against the current manifests, so a flow built from older definitions can pass the embedded check and still render with missing edges. When the current manifests cannot be loaded, the check is skipped with a warning. - With
--governance, any agent node whose configuration (model, tools, policies) conflicts with the fetched enforcements is flagged. - Node and edge IDs that start with
previeware errors: the converter that packs the flow leaves those nodes and edges out, souip maestro flow packanduip maestro flow debugfail. Rename the node or edge, and update its edges and$varsreferences. Sticky notes are exempt.
Examples
# Structural validation only (no login required)
uip maestro flow validate invoice-flow.flow
# Full validation including governance policy for agent nodes
uip maestro flow validate invoice-flow.flow --governance
# Validate the project's main .flow file
uip maestro flow validate ./my-flow-project
# Fail on expression and script type errors (warnings by default)
uip maestro flow validate invoice-flow.flow --strict-expressions
# Validate against freshly fetched node manifests, bypassing the 30-minute cache
uip maestro flow validate invoice-flow.flow --force
# Structural validation only (no login required)
uip maestro flow validate invoice-flow.flow
# Full validation including governance policy for agent nodes
uip maestro flow validate invoice-flow.flow --governance
# Validate the project's main .flow file
uip maestro flow validate ./my-flow-project
# Fail on expression and script type errors (warnings by default)
uip maestro flow validate invoice-flow.flow --strict-expressions
# Validate against freshly fetched node manifests, bypassing the 30-minute cache
uip maestro flow validate invoice-flow.flow --force
Data shape (--output json)
On success:
{
"Code": "FlowValidate",
"Data": {
"File": "invoice-flow.flow",
"Status": "Valid"
}
}
{
"Code": "FlowValidate",
"Data": {
"File": "invoice-flow.flow",
"Status": "Valid"
}
}
When the file is valid but has warnings, Data also carries Warnings: a string with the warning count followed by one - [<path>] <message> line per warning.
On validation failure, the command exits with code 1 and returns a Failure result. Message is Validation failed for <file>, and Instructions holds the error count followed by one - [<severity>] [<path>] <message> line per issue.
See also
uip maestro flow debug— dynamic validation via Studio Webuip maestro flow pack— pack a validated project- Flow overview