uip rpa get-errors
uip rpa get-errors returns the validation diagnostics — errors, warnings, informational messages — for a single file or the entire open project. By default, the verb forces Studio to re-run validation before collecting results so the output is fresh; pass --skip-validation if you want what is currently displayed in the designer (which may be stale).
The verb runs through Studio's validation pipeline and therefore requires a Windows runner. Scoping to a single file with --file-path is significantly faster than re-validating a large project.
Synopsis
uip rpa get-errors [--file-path <string>] [--skip-validation] [--min-severity { error | warning | info | verbose }]
Options
| Flag | Description |
|---|---|
--file-path <string> | Project-relative path of the file to inspect. If omitted, diagnostics for the whole project are returned. |
--skip-validation | Return cached diagnostics from the last validation pass instead of re-validating. May be stale. Default: false. |
--min-severity <string> | Lowest severity to include — error, warning, info, or verbose. error returns only errors; warning adds warnings; info adds informational messages; verbose returns everything. Default: warning. |
For the complete option list on your installed tool version, run:
uip rpa get-errors --help
Examples
# Errors and warnings for one file (fastest)
uip rpa get-errors --file-path Main.xaml
# Hard errors only across the entire project — quick CI gate
uip rpa get-errors --min-severity error
# Use the diagnostics already shown in the designer, no re-validation
uip rpa get-errors --skip-validation
Related
uip rpa run-file— typical reason to check diagnostics is right before or after running a file.uip rpa analyze— broader workflow analyzer, separate from validation diagnostics.uip rpa get-analyzer-rules— see which rules contribute to the diagnostics surface.