UiPath LLM Client [v1.17.1]

[1.17.1] - 2026-07-17

Added

• ModelNotFoundError — raised by UiPathBaseSettings.get_model_info when a model name is absent from the discovery API response. It subclasses both ValueError (so existing except ValueError handlers are unaffected) and UiPathError (so it is catchable across the UiPath LLM error taxonomy), and carries the new UiPathLLMErrorCode.MODEL_NOT_FOUND code. This lets callers distinguish a genuine discovery-miss from the other ValueErrors the factory/settings code can raise (unsupported vendor, missing agenthub_config, invalid kwargs) instead of matching on message text.
• UiPathLLMErrorCode.MODEL_NOT_FOUND semantic error code.

UiPath LangChain Client [langchain-v1.17.1]

[1.17.1] - 2026-07-17

Changed

• Picks up core uipath-llm-client 1.17.1, which adds ModelNotFoundError (raised by get_model_info on a discovery-miss) and the UiPathLLMErrorCode.MODEL_NOT_FOUND code. Bumped the uipath-llm-client floor to >=1.17.1.

UiPath LLM Client [v1.17.0]

[1.17.0] - 2026-07-14

Changed

• Restored retry parity with the legacy uipath-langchain-python chat-client retryers (BedrockRetryer) that the shared transports replaced. Under throttling that outlasted the previous budget, runs that the legacy client absorbed silently were now failing.
  • Default retry budget is now 5 attempts (was 3) with exponential backoff starting at 5s (was 2s) capped at 120s (was 60s) — waits of ~5/10/20/40s, an absorption window of roughly 75s instead of ~6s.
  • Retry-After / x-retry-after is honored on any error status, not just 429: the header caps the wait for every UiPathAPIError, and its presence forces a retry even for otherwise non-retryable statuses (an explicit server retry request). retry_after moved from UiPathRateLimitError up to UiPathAPIError.
  • HTTP 524 (Cloudflare origin timeout) is retryable again via the new UiPathOriginTimeoutError; 529 remains retryable.
  • Connection-level failures are retried: httpx.TimeoutException (connect/read/write/pool timeouts), httpx.ConnectError, and httpx.RemoteProtocolError — the union of what the legacy Bedrock (botocore timeout/connection errors) and Vertex (httpx timeouts, connect errors, remote-protocol errors) retryers handled.

Added

• UiPathOriginTimeoutError (HTTP 524), exported from uipath.llm_client.

UiPath LangChain Client [langchain-v1.17.0]

[1.17.0] - 2026-07-14

Changed

• Default max_retries on UiPathBaseLLMClient raised from 3 to 5 for parity with the legacy uipath-langchain-python chat-client retryers. Requires uipath-llm-client>=1.17.0, which also restores the legacy backoff window (5s initial / 120s cap), honors Retry-After on any status, and retries 524 and connection-level failures.

UiPath LLM Client [v1.16.3]

[1.16.3] - 2026-07-13

Fixed

• Request headers that differ only by casing are now merged before authentication in the shared synchronous and asynchronous HTTPX clients. This prevents provider SDKs from emitting duplicate fields such as User-Agent and user-agent, while preserving intentionally repeated values that use the winning spelling.

UiPath LLM Client [v1.16.2]

[1.16.2] - 2026-07-06

Added

• UiPathLLMErrorCode — a public string enum of stable semantic error codes independent of provider exception types or provider-specific message text. It currently includes UNSUPPORTED_MIME_TYPE.
• UiPathError now carries optional semantic context: error_code (a stable machine-readable identifier, preferably from UiPathLLMErrorCode) and detail (best-effort diagnostic detail from the mapped lower-level error).

Changed

• as_uipath_error now resolves errors with HTTP status as authoritative: the cause chain is scanned for an httpx.Response first, so a real status always outranks a client-side classifier match elsewhere in the chain (which may be incidental __context__ rather than the failure). Only when no response exists anywhere is the error offered to the _CLIENT_SIDE_CLASSIFIERS registry (extension point for future non-HTTP semantic codes, e.g. the unsupported-MIME case). Previously client-side classifiers ran first and could mask an authenticated/rate-limited/server error carrying an unrelated marker.

UiPath LLM Client [v1.16.0]

[1.16.0] - 2026-07-03

Added

• Per-service URL overrides for local development. build_base_url now consults resolve_service_url(endpoint_path) (from uipath.platform.common) before constructing the final URL. When a UIPATH_SERVICE_URL_<SERVICE> env var is set (e.g. UIPATH_SERVICE_URL_AGENTHUB=http://localhost:8080), requests are redirected to that local server with the org/tenant and service prefix stripped. Without an override, behaviour is unchanged — the URL is still {base_url}/{endpoint_path}.

UiPath LLM Client [v1.15.1]

[1.15.1] - 2026-07-03

Changed

• Bumped uipath-platform to >=0.1.91 — 0.1.89/0.1.90 crashed with a circular-import ImportError when importing IdentityService (fixed upstream in UiPath/uipath-python#1787).

UiPath LangChain Client [langchain-v1.16.1]

[1.16.1] - 2026-07-03

Fixed

• import uipath_langchain_client no longer requires the bedrock extra (regression in 1.15.1).

UiPath LangChain Client [langchain-v1.16.0]

[1.16.0] - 2026-07-03

Changed

• Picks up core uipath-llm-client 1.16.0, which adds per-service URL overrides for local development (UIPATH_SERVICE_URL_<SERVICE> env vars). Bumped the uipath-llm-client floor to >=1.16.0.