feat: add escalation memory cache and ingest by mjnovice · Pull Request #805 · UiPath/uipath-langchain-python

mjnovice · 2026-04-23T23:35:36Z

Depends on #793

Summary

Adds memory cache check (_check_escalation_memory_cache) before HITL task creation — cache hit skips human escalation
Adds outcome ingest (_ingest_escalation_memory) after human resolution to persist for future recall
Gated by isAgentMemoryEnabled + memorySpaceId on the escalation resource config
Search settings (threshold, searchMode, fieldSettings) read from resource memory config
Span attributes (fromMemory, savedToMemory) for trace observability
Extracts completed_by_user email for memory ingest userId

Test plan

tests/agent/tools/test_escalation_memory.py — 7 tests for cache check, ingest, and space ID resolution
tests/agent/tools/test_escalation_tool.py — all 37 tests pass
tests/agent/tools/test_ixp_escalation_tool.py — all 16 tests pass
Ruff lint passes

🤖 Generated with Claude Code

mjnovice · 2026-04-24T00:03:57Z

Transferring review comments from @andreitava-uip on #793 that apply to escalation memory (now in this PR):

No private repo references in public library — Remove comments referencing .cs files from private repos. Applicable to all comments.
Move memory helpers to a separate file — The memory helpers are completely standalone and should be in their own file rather than in escalation_tool.py.
Hardcoded CONTINUE outcome — Is hardcoding CONTINUE correct? Do we not commit to memory other outcomes?

mjnovice · 2026-04-24T00:04:35Z

Another comment from @andreitava-uip on #793:

Lazy load question (escalation_tool.py, around line 438) — "Any reason for the lazy load?"

mjnovice · 2026-04-24T00:04:44Z

Another comment from @andreitava-uip on #793:

Hardcoded CONTINUE in tests (test_escalation_memory.py, line 58) — "This mirrors my other comment over whether the action result should get hardcoded to CONTINUE"

Adds memory integration to the escalation tool: - Before creating HITL task: escalation_search_async() checks for cached answer - Cache hit returns cached result immediately, skipping human escalation - After human resolution: escalation_ingest_async() persists outcome - Gated by isAgentMemoryEnabled + memorySpaceId on the escalation resource - Search settings (threshold, searchMode, fieldSettings) read from resource config - Span attributes (fromMemory, savedToMemory) for trace observability Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

When no fieldSettings are configured in the agent definition, field_weights should be None (search all fields with default weights) rather than raising a validation error. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

This reverts commit f6751d3.

Escalation memory ingest relies on traceId/spanId to reconstruct the escalation tool input and output from LLMOps. Reading the current span after HITL resume can point at the resumed run context instead of the original escalation child span, which lets ingest return 200 while creating blank memory rows. Consume the span context supplied through tool metadata, fall back to the current span only when metadata is missing, and normalize fallback trace ids through UIPATH_TRACE_ID so the ingest payload uses the same exported LLMOps trace id as span upserts. Treat an unsearchable escalation memory retrieval request as a cache miss rather than raising ValueError. This covers empty input/configured-field mismatches and keeps escalation memory as an optimization instead of blocking task creation.

sonarqubecloud · 2026-05-14T02:46:20Z

Quality Gate failed

Failed conditions
89.0% Coverage on New Code (required ≥ 90%)

See analysis details on SonarQube Cloud

mjnovice force-pushed the feat/memory-loop-integration-scaffold branch 4 times, most recently from 8c8b6b1 to 4817a5e Compare April 24, 2026 06:42

Base automatically changed from feat/memory-loop-integration-scaffold to main April 24, 2026 07:12

gcuip reviewed Apr 24, 2026

View reviewed changes

Comment thread src/uipath_langchain/agent/tools/escalation_tool.py Outdated

Comment thread src/uipath_langchain/agent/tools/escalation_tool.py Outdated

mjnovice force-pushed the feat/escalation-memory branch from 4938bc0 to 7bd14ea Compare April 24, 2026 16:30

smflorentino reviewed Apr 24, 2026

View reviewed changes