What problem does it solve? UiPath automations fail with cryptic errors, hangs, or silent wrong results, and finding the root cause requires correlating job logs, traces, configuration, and workflow source across many products. This Skill runs a structured causal investigation that routes error signals to documented playbooks and verifies the root cause before proposing a fix. ## Core Features & Use Cases - Signal-based routing: Extracts exception classes, error codes, and faulting activities from raw CLI output and greps a playbook corpus to match the exact failure pattern. - Cross-domain correlation: Follows wrapped exceptions and linked entity keys one hop across Orchestrator, Maestro, Integration Service, UI Automation, and other domains to find the originating fault. - Gated resolution: Verifies every conclusion against a six-point evidence checklist, then presents sourced fixes with an approval gate before any change is applied. - Use Case: A user pastes a faulted Orchestrator job error. The Skill anchors the job, extracts the inner exception, matches the playbook, confirms the cause with runtime evidence, and presents the exact fix with citations. ## Quick Start Ask the assistant to investigate why a specific UiPath job, queue item, or automation failed using the pasted error message or job ID.
