fix: categorize analyze files 5xx errors as system - #1019
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR aligns the Analyze Files tool’s error normalization with the main agent LLM execution path by converting provider HTTP failures into structured AgentRuntimeErrors, and it updates the HTTP-status → UiPathErrorCategory mapping so 5xx provider responses are surfaced as SYSTEM (while preserving status/detail where available).
Changes:
- Normalize Analyze Files LLM call exceptions (new + legacy provider SDK errors) into the existing structured agent error taxonomy.
- Update provider HTTP error categorization so 5xx statuses map to
UiPathErrorCategory.SYSTEM(instead ofUNKNOWN). - Add/adjust tests to validate 5xx categorization and ensure unknown remains for unclassified statuses.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| uv.lock | Bumps package version to 0.15.1 in the lockfile. |
| pyproject.toml | Bumps project version to 0.15.1. |
| src/uipath_langchain/agent/tools/internal_tools/analyze_files_tool.py | Adds structured exception mapping for provider/LLM-client/legacy exceptions during Analyze Files LLM invocation. |
| src/uipath_langchain/agent/exceptions/licensing.py | Introduces status→category helper and maps 5xx provider HTTP errors to SYSTEM. |
| tests/agent/tools/internal_tools/test_analyze_files_tool.py | Adds a test ensuring provider 5xx errors are categorized as SYSTEM for Analyze Files. |
| tests/agent/test_licensing.py | Updates/adds tests for 5xx→SYSTEM and keeps unclassified statuses as UNKNOWN. |
radu-mocanu
force-pushed
the
fix/analyze-files-provider-error-categorization
branch
from
August 3, 2026 00:05
7950cc4 to
640414f
Compare
radu-mocanu
force-pushed
the
fix/analyze-files-provider-error-categorization
branch
from
August 3, 2026 06:27
640414f to
b2b9d54
Compare
|
andreitava-uip
approved these changes
Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Analyze Filesprovider5xxfailures asSystem HTTPerrorsUnknownfailureWhy
Analyze Filesinvokes the LLM outside the main agent node, so provider 500 responses bypassed existing normalization and appeared as Unexpected Error with an Unknown category. This applies the same taxonomy used by the main LLM path.