Skip to content

🍒 [v1.207] fix(uipath-maestro-bpmn): fetch a record by a run-time key with an operation that needs no design-time lookups - #4996

Merged
rockymadden merged 1 commit into
release/v1.207from
claude-fix-bpmn-connections-dec910-CP-to-release-v1-207
Nov 19, 2026
Merged

rockymadden merged 1 commit into
release/v1.207from
claude-fix-bpmn-connections-dec910-CP-to-release-v1-207

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

What

connectors.md: two lines after the LOOKUP_RUNTIME_VALUE note. When a step reads a record by a key the process is given and the operation also needs lookups nobody supplies, never derive them from the key, and never pin one while a generic Retrieve whose required inputs are all plain can read the record; list the connector's Retrieves (registry search retrieve --connector <KEY> --limit 50 --output json, re-run with --limit <TOTAL> when Data.Total is higher) and read each field reference; with none, ask the user, or, when nobody will answer, pick a listed value and name it on Assumed:. Studio Web flavor: registry describe needs --object for a generic operation.

New eval connector_features/runtime_record_key + _shared/check_runtime_record_key.py: a Jira issue looked up by an input key, graded on the compiled BPMN (no node sends project/issuetype, run-time or pinned; some node reads by a run-time key, path parameter or jql).

Why

Dogfood row 17 (Confluence 91373076800). Autopilot (stock skills ≈ main on these lines, Haiku 5.5, row-17 prompt verbatim; one clarifying question, answered "Slack: Send Message to Channel") built Jira curated get-issue with project: =vars.projectKey, issuetype: =vars.issueType → check warning LOOKUP_RUNTIME_VALUE. The skill said "fix it in your source" without saying how; terminal agents on main derived project from the key, or pinned one project.

Row-19 lessons: what a repro showed

Lesson Repro Change
Run-time key needs a record-retrieval op, not one needing design-time lookups Shown (Autopilot + terminal) This PR
Check solution resources list --source remote before binding Not shown: locally personal-workspace connections are listed and resources add --cloud-key succeeds; row 18's refused key is itself in the remote list, so the check would not have caught it. Refusal comes from Studio Web's ManageSolutionResources, not the CLI None
Event triggers needing BYOA Already covered: library md "Requires a BYOA connection" + check EVENT_BYOA_UNVERIFIED None
"Variables should be input arguments" → start-event inputs Not shown: the run declared every value with .input(). How inputs are read is #6 (#4892) None

Evidence

Terminal coder-eval (claude-code, popoc; the preflight criterion fails locally only because popoc has no Shared/uipath-maestro-flow):

  • main: FAIL — project/issuetype derived from the key.
  • this branch: PASS on every wording iteration, incl. the final head (3b646b2) — get-record on curated_issue, issueId: =vars.issueKey. An early, looser wording let the agent pin one project; the grader and the line were tightened after that run.
  • Mailchimp (caller passes audience id and email, so the curated op's lookup is supplied and the rule does not require a change): this branch → get-record on lists::members, check clean; an earlier wording kept curated get-subscriber, also check clean. Shows no harm on another connector, not the rule firing. Not run on main.

Autopilot after-run (branch build at 3b646b2, Haiku 5.5, row-17 prompt verbatim, new chat, Solution 73 a42ea244-b4cf-4687-f6f5-08df455df8a5):

  • Swap proof: in-iframe getBundledPluginReleases() = 1.0.0-f2ff718ecaf8, equal to sha256(dist/index.json) f2ff718e…5ea. Served uipath-maestro-bpmn/references/connectors.md and SKILL.md from :5052 match the build (sha1 3c30e6f0…, fb5e629d…).
  • Jira step: search-issues-by-jql with jql: "project = " + vars.projKey + " AND key = " + vars.issKey. No project/issuetype lookups, and check reports no LOOKUP_RUNTIME_VALUE on Jira. The new eval's grader passes on this output (OK: searchIssue reads the record by run-time ['jql'] alone).
  • Inputs: .input("projectKey"), .input("issueKey"), .input("channel").
  • Remaining check/validate findings:
    • CONNECTION_BINDING_NOT_GUID ×2 and MISSING_BINDING ×2: both connections were left unbound by answer.
    • LOOKUP_RUNTIME_VALUE on the Slack channel: Autopilot warned about this before building, and the answer chose the runtime input.
    • LOOKUP_LITERAL_ID on send_as: bot: informational.
    • None of these is this fix's case.
  • Clarifying questions: the before-run asked 1, the after-run asked 5, so the answers can't be identical. Each was answered as a real user would and no question was dismissed. Connections stayed unbound, as in the before-run, whose bindings were empty.
    1. Summary agent: "Build a new summary agent in this solution".
    2. Jira connection: "Leave Jira unbound for now".
    3. Slack connection: "Leave Slack unbound for now".
    4. Channel: "Runtime input, passed when the process starts".
    5. Issue: "Issue key passed at start".
  • Studio Web designer screenshot: Start → Search Issues by JQL → buildIssueText → Summarize → Send Message to Channel → End. The red markers are the unbound connections.
  • Stock restored afterwards: the iframe release is back to 1.0.0-a8b15ef850db.

Unverified: a live debug run of get-record (no own Jira connection on the test tenant).

🤖 Generated with Claude Code


Automatically cherry-picked from #4897 to release/v1.207 by @rockymadden.

…eration that needs no design-time lookups (#4897)

* fix(uipath-maestro-bpmn): fetch a record by a run-time key with an operation that needs no design-time lookups

A curated get (Jira Get Issue) also asks for lookups the caller never
supplies (project, issue type). Agents filled them from inputs
(LOOKUP_RUNTIME_VALUE, rejected at run time) or pinned one project
(works for that project only). Point them at the object's generic
Retrieve, which reads the record by its key. Adds an eval grading the
outcome on the compiled BPMN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review round 1: find the right object, fallback, grader multi-node and jql, accurate LOOKUP_RUNTIME_VALUE wording

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review round 2: cut the Needs fallback, general search hint, field reference, --limit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review round 3: list every Retrieve on the connector, plain required inputs, ask when none

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review round 4: headless default for the no-Retrieve case, read Data.Total

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review round 5: say which value and where it is reported

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* review: grader requires a process-input key, a GET read and no literal project in jql

A literal key wrapped in an expression, a project-pinned jql and a non-read
operation all passed. Negative fixtures guard each.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@rockymadden
rockymadden merged commit f5e7ba1 into release/v1.207 Nov 19, 2026
3 checks passed
@rockymadden
rockymadden deleted the claude-fix-bpmn-connections-dec910-CP-to-release-v1-207 branch November 19, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants