Repository navigation
fix(guardrails): label guardrail provider errors in validation details [AL-673] - #1189
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified for the change distinguishing guardrail evaluation errors from policy violations.
No open issues 🎉
What changed in this PR
This PR distinguishes guardrail evaluation errors from policy violations in validation details, while preserving fail-closed routing and configured actions.
Changes:
- Labels provider, internal, and rate-limit errors as guardrails that could not be evaluated.
- Adds parametrized tests for labelled details and unchanged failure routing.
- Bumps the package to
0.18.54and requiresuipath-core>=0.5.34.
| File | Description |
|---|---|
uv.lock |
Updates package version and minimum core dependency metadata. |
tests/agent/guardrails/test_guardrail_nodes.py |
Tests failure routing and labelled details for all three error types. |
src/uipath_langchain/agent/guardrails/guardrail_nodes.py |
Labels evaluation errors in guardrail validation details. |
pyproject.toml |
Bumps the release version and minimum core dependency. |
Review effort: Balanced
…s [AL-673] When the backend cannot evaluate a guardrail (provider error, internal error, rate limit), uipath-platform 0.2.42+ still returns validation_failed (fail-closed) and sets error_type. The failure node now gets "Guardrail could not be evaluated (<error_type>): <reason>" as the details, so Log and Escalate actions no longer report a provider error as a policy violation. Routing is unchanged. Requires uipath-core>=0.5.34 and bumps to 0.18.55. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
apetraru-uipath
force-pushed
the
fix/al-673-guardrail-error-details
branch
from
November 2, 2026 21:56
57127e1 to
71e91e5
Compare
|
andreizdrali-uipath
approved these changes
Nov 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.
Follow-up to UiPath/uipath-python#1956. Jira: AL-673, from SRE-687087.
Problem. On 2026-10-22 in prod, an LLM-as-Judge guardrail returned
PROVIDER_ERROR("temperatureis deprecated for this model.") 90 times. The SDK mapped each one tovalidation_failed, so the guardrail action ran and the runs were reported as guardrail violations, although the guardrail was never evaluated.Change. Since uipath-platform 0.2.42, these results are still
validation_failed(fail-closed) but now also carryerror_type(provider_error,internal_error,rate_limit_exceeded). Whenerror_typeis set,_create_validation_commandwritesGuardrail could not be evaluated (<error_type>): <reason>toguardrail_validation_details. Log and Escalate actions now show that the guardrail could not be evaluated. Routing is unchanged: the run still goes to the failure node and the configured action still runs.Requires
uipath-core>=0.5.34(theGuardrailValidationErrorTypeenum);uipath-platform>=0.2.43was already required. Bumps the version to 0.18.55.The backend fix that stops the judge from sending
temperatureto models that reject it is UiPath/Agents#6797.Tests. A parametrized
_create_validation_commandtest covers each error type: the run routes to the failure node with labelled details. The existing tests confirm that details are unchanged whenerror_typeis not set. Locally: the full suite (4159 passed), ruff and mypy are clean.🤖 Generated with Claude Code