- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip docsai
- 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-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- restore
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- Migration
- Reference & support
Syntax and options for `uip maestro flow incident`, which reads tenant-wide or single-record incidents raised during Flow process execution.
uip maestro flow incident reads incidents — unhandled errors raised during Flow process execution — either as tenant-wide summaries or as a single record by ID. The command name is singular (incident) even though the file and sidebar entry say incidents.
All subcommands require uip login and honor global options. Exit codes follow the standard contract.
Synopsis
uip maestro flow incident summary
uip maestro flow incident get <incident-id> --folder-key <key>
uip maestro flow incident summary
uip maestro flow incident get <incident-id> --folder-key <key>
For incidents scoped to a specific process or instance, use:
uip maestro flow processes incidents <process-key>— all incidents for one process.uip maestro flow instance incidents <instance-id>— all incidents for one running instance.
uip maestro flow incident summary
Get a tenant-wide rollup of incidents across Flow processes.
Arguments
None.
Options
None beyond globals.
Data shape (--output json)
{
"Code": "IncidentSummary",
"Data": [ /* array of incident summaries */ ]
}
{
"Code": "IncidentSummary",
"Data": [ /* array of incident summaries */ ]
}
The list is returned unfiltered — use --output-filter with a JMESPath query to extract specific fields.
uip maestro flow incident get
Get a single incident by ID.
Arguments
<incident-id>(required) — incident ID. URL-encoded automatically.
Options
--folder-key <key>(required) — folder key.
Data shape
{
"Code": "IncidentGet",
"Data": { /* incident details */ }
}
{
"Code": "IncidentGet",
"Data": { /* incident details */ }
}
Examples
# Tenant-wide incident rollup
uip maestro flow incident summary
# Extract just the incident IDs and counts
uip maestro flow incident summary --output-filter "[*].{processKey:processKey,count:incidentCount}"
# Get a specific incident
uip maestro flow incident get "inc_abcdef1234" --folder-key <folder-key>
# Tenant-wide incident rollup
uip maestro flow incident summary
# Extract just the incident IDs and counts
uip maestro flow incident summary --output-filter "[*].{processKey:processKey,count:incidentCount}"
# Get a specific incident
uip maestro flow incident get "inc_abcdef1234" --folder-key <folder-key>
See also
uip maestro flow instance incidents— incidents for one instanceuip maestro flow processes incidents— incidents for one process definitionuip maestro flow instance retry— remediate a faulted instance- Flow overview