uip maestro incidents

uip maestro incident reads incidents — unhandled errors raised during Maestro 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 incident summary
uip maestro incident get <incident-id> --folder-key <key>

For incidents scoped to a specific process or instance, use:

• uip maestro processes incidents <process-key> — all incidents for one process.
• uip maestro instance incidents <instance-id> — all incidents for one instance.

uip maestro incident summary

Get a tenant-wide rollup of incidents across Maestro processes.

Arguments: none. Options: none beyond globals.

Data shape (--output json):

{
  "Code": "IncidentSummary",
  "Data": [ /* array of incident summaries */ ]
}

uip maestro 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 */ }
}

Examples

# Tenant-wide rollup
uip maestro incident summary

# Extract a terse view
uip maestro incident summary --output-filter "[*].{processKey:processKey,count:incidentCount}"

# Fetch one
uip maestro incident get "inc_abcdef1234" --folder-key <folder-key>

See also

• uip maestro instance incidents — incidents for one instance
• uip maestro processes incidents — incidents for one process definition
• uip maestro instance retry — remediate a faulted instance
• Maestro overview