Repository navigation
fix(uipath-agents): check the IS connection can see the value the user named - #4910
Conversation
…oject When several connections exist for a connector, the agent took the first one even though its Jira site had no project AB, so the issue fields never loaded and it fell back to the raw `issue` object. Step 3 now recommends the connection that can see what the task names, and Step 6 says to retry the listing on each enabled connection on a 404 and never fall back to the raw object. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Claude finished @astridstaicu's task in 44s —— View job SummaryTwo additions to the low-code IS guide ( Change-by-Change Review1. Step 3: recommend the connection that can see the named entity (
|
| Area | Status | Notes |
|---|---|---|
| Frontmatter | OK | Not touched |
| E2E Tests | Issue | No regression task for picking among several connections (eval rerun pending) |
| Skill Body | OK | Not touched |
| References & Assets | Issue | Shared resourceKey across tools not handled when switching connection |
| Repo Hygiene | OK | Change limited to one skill; no secrets or personal paths; no new links |
Issues for Manual Review
- Confirm that
uip is resources run listgives a recognisable 404 for a missing project. The agent needs to tell "not on this site" apart from transport or authentication errors. - Confirm that
uip solution resources refreshpicks up the switched connection frombindings_v2.jsonwith no other step. The PR text says "when adding the connection to the solution" but doesn't name a command.
Conclusion
The fix matches the root cause found in the transcripts and is small. Approve after addressing the shared-resourceKey gap. Telling the user about the switch is also recommended. The other points are optional.
… named value Replace the silent retry across connections with: list which enabled connections can see the value and let the user choose; when no one can answer, use the one that sees it and say so. Drop the repeated raw-object rule (Step 4 already has it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Why
After #4868, helpdesk-jira-triage still fails on Studio Web (eval run
adhoc-2026-11-18_10-24-40, build 14320034) with "no Jira create-issue IS tool". The tenant has three Jira connections, and only one of them,is-sandboxes-test…sandbox-380(ac8506ff…), can see project AB. The other two, includingskills-evals-golden-jira, answerNo project could be found with key 'AB'when the agent listsproject/AB/issuetypes. The project is either missing from those sites or the connection's account can't browse it.ac8506ff, and built the tool oncurated_create_issue.describe curated_create_issuereturns no summary or description, so it switched to the rawissueobject, which the grader rejects.The skill told the agent to recommend the default enabled connection, and never said to check that the connection can see what the user named.
What
integration-service.md:resourceKey, and the solution. If none can see it, tell the user and stop.This is canonical text with no Studio Web override, so both trees change.
The task's setup has a related problem, and this PR does not fix it. The prompt says "using the existing JIRA Connection", but the eval's own
skills-evals-golden-jiraconnection can't see project AB. Giving that connection access to AB, or naming the connection in the prompt, would make the task deterministic.Verification
npm run skills:validate,skills:check-linksandskills:buildpass, and the new text is in the built studioweb tree.ac8506fflists AB.🤖 Generated with Claude Code