Troubleshoot with UiPath for Coding Agents

Coding Agents for Troubleshooting brings conversational diagnostics to the UiPath platform. Describe a failure in plain English from any terminal on your machine — including the integrated terminal in UiPath Studio — and the skill triages the issue, ranks likely causes, tests each hypothesis against live platform data through uip, and tells you exactly what went wrong and how to fix it.

The Troubleshoot skill is part of the UiPath skill catalog and installs into your coding agent via uip skills install.

Mode de fonctionnement

A diagnostic session follows the same four-stage flow regardless of failure type:

1. Triage — Classify the failure scope from the user's description, the job or process identifier, or the error message. If the input is ambiguous, the skill asks a clarifying question.
2. Generate hypotheses — Produce a ranked list of possible causes, drawing on the relevant domain playbook and any evidence gathered during triage.
3. Test hypotheses — Confirm or eliminate one hypothesis at a time. The skill fetches logs, traces, queue items, healing data, configuration, and audit events through uip to gather evidence.
4. Resolution — Present the root cause, the chain of events that produced the failure, and a concrete fix. The skill asks for explicit approval before changing anything.

The user can be involved at four moments: clarifying the scope during triage, supplying extra context for hypothesis generation, providing source code or configuration files when needed, and approving recommended fixes.

What you can diagnose today

The Troubleshoot skill covers the following domains. You describe the problem; the skill fetches the evidence and returns a root cause.

Domaine (Domain)	What you can diagnose	Example ask
RPA	Failed jobs (SelectorNotFoundException, TimeoutException, and similar), selector mismatches, queue item failures, Healing Agent data analysis	"Why did the InvoiceBot job fail this morning?"
Orchestrator	Stuck or faulted jobs, permission and role issues, deployment and publishing errors, queue configuration problems	"Why is my robot not picking up items from the Finance queue?"
Maestro	Faulted process instances, step-level failures, incidents, multi-domain failure chains that involve agents or RPA	"Why did the approval process instance fault on step 3?"

Support for other UiPath domains is already in place but still being deepened. More domains and richer diagnostics are on the way.

The skill operates with the same access you have. If you cannot read certain logs or folders as a signed-in user, the skill cannot read them either.

Prérequis

1. UiPath skills installed for your agent. See Using UiPath CLI with Coding Agents for the install command per agent.
2. A logged-in session (uip login). See Authentication.

Étapes

Run the setup described here Using UiPath CLI with Coding Agents once per machine. After that, the skill is available in every session.

Launch your coding agent from any terminal on your machine or from the integrated terminal in UiPath Studio, then start a diagnostic session by entering /uipath-troubleshoot to invoke the skill explicitly, or by describing the problem directly — for example, "My job abc-123 failed, what happened?"

Respond to the skill's follow-up prompts. Answer clarifying questions in plain English, and share source code, configuration files, or other artifacts when the skill requests them.

The skill prints a structured root-cause summary — the failing component, the chain of events that produced the failure, supporting evidence from logs and traces, and a recommended fix. Before changing anything on your machine or in your tenant, the skill asks for explicit approval.

The following example shows a session run from the integrated terminal in UiPath Studio:

Tips for effective sessions

Treat the skill like a colleague helping you debug; context and back-and-forth improve the outcome:

• Be specific. Job IDs, process names, queue names, and exact error messages let the skill skip clarifying rounds.
• Keep the conversation going. If the first recommendation does not match what you observe, say so. Phrases like "that's not it", "I already checked that", or "dig deeper" keep the investigation moving.
• Redirect when needed. If the skill follows the wrong thread, correct it — for example, "the issue is not with permissions; the job ran fine yesterday".
• Share files when asked. XAML, project.json, configuration files, and similar artifacts sharply improve diagnosis quality.
• Match access to expectations. The skill uses your signed-in uip session and inherits your permissions. If you cannot view a log, the skill cannot either.

Voir également

• Skills — the broader skills mechanism
• Using UiPath CLI with Coding Agents — installing the UiPath skill catalog into Claude Code, Cursor, GitHub Copilot, Gemini CLI, Codex, and OpenCode
• Managing tools and skills — day-to-day maintenance