revert: process tool folder resolution fallback (#1038)

[robert-ursu]

Reverts the folder resolution change from #1038 (a1bd280). Version bumped 0.16.6 → 0.16.7.

Why

#1038 broke tool resolution for lowcode agents on serverless. The alpha CI agent (SimpleAgent on the PythonAwsTests / PythonK8sTests tenants) fails on every run with:

Failed to execute tool 'SumAgent'
Could not find folder for tool 'SumAgent'. Please check if the folder exists and is accessible by the robot.

Serverless.RuntimeVersions pins it to the package version, not to anything on the agent side — the agent itself hasn't changed:

Date (UTC)	uipath-agents	uipath-langchain	SimpleAgent
08-11 → 08-13	200.0.5 → 200.0.12	0.16.2 / 0.16.3	✅
08-18 / 08-21	200.0.0 / 200.1.0	0.15.2	✅
08-15 / 08-20	200.0.13	0.16.5	❌
08-21	201.0.0	0.16.5	❌
08-25	201.0.4	0.16.6	❌

Fails iff uipath-langchain >= 0.16.5 — the version #1038 shipped in.

Root cause

The change introduced this precedence in create_process_tool:

folder_path = get_execution_folder_path() or resource.properties.folder_path
folder_key = get_execution_folder_key() if not folder_path else None

On a serverless job UIPATH_FOLDER_PATH is unset, so it falls through to resource.properties.folder_path. For anything exported from Agent Builder / Solutions that value is the literal "solution_folder" placeholder baked into agent.json at export time. It's truthy, so:

• folder_key is forced to None and the UIPATH_FOLDER_KEY fallback the PR was written for never fires — it's dead code for every packaged agent
• StartJobs goes out with folderPath="solution_folder", Orchestrator rejects it (code 1100), and it surfaces as the "Could not find folder" message above

Before the change, folder_path=None was passed and the SDK resolved the process in the job's own execution folder — the correct behaviour for these agents. Lowcode agents never carry a usable folderPath; the real value arrives via binding overwrites at runtime.

The eval-serverless failure #1038 was chasing is a missing binding overwrite / fpsProperties advertisement on the eval path, not something to compensate for in the runtime.

Follow-up (agreed in this thread, separate PRs)

• uipath-langchain: send resource.properties.folder_path literally, so coded agents can pass a folder explicitly
• uipath-agents: force the folder in the agent definition to None, since lowcode agents always carry the solution_folder placeholder and rely on binding overwrites for the real value
• fix: never send the solution_folder sentinel as a folder path #1044 addresses the same symptom by special-casing the solution_folder sentinel — a band-aid on top of this regression; superseded by the above

Reverting now to unblock the pipeline; the proper fix lands on its own timeline.

Testing

• Full suite green (2684 tests), ruff check / ruff format clean, httpx client linter clean
• TestProcessToolFolderResolution (added by fix: process tool folder fallback when UIPATH_FOLDER_PATH is unset #1038) removed along with the code it covered

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR reverts the process-tool folder resolution fallback introduced in #1038, restoring the prior serverless behavior where process tools resolve within the execution context rather than using design-time folderPath. It also bumps the package version from 0.16.6 to 0.16.7 to ship the revert.

Changes:

• Revert create_process_tool folder resolution to only use UIPATH_FOLDER_PATH, removing UIPATH_FOLDER_KEY/resource-folder fallbacks and related span metadata.
• Remove the folder-resolution test suite added in #1038 and update remaining assertions to match the reverted invoke_async call signature.
• Bump version to 0.16.7 and refresh uv.lock accordingly.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/uipath_langchain/agent/tools/process_tool.py	Reverts folder resolution logic to only use get_execution_folder_path() and removes folder_key usage/metadata.
src/uipath_langchain/_utils/_environment.py	Removes get_execution_folder_key() helper, leaving only folder path env lookup.
src/uipath_langchain/_utils/__init__.py	Stops exporting get_execution_folder_key from _utils.
tests/agent/tools/test_process_tool.py	Deletes folder fallback tests and updates call assertions to omit folder_key=None.
pyproject.toml	Version bump 0.16.6 → 0.16.7.
uv.lock	Lockfile updated for the version bump and refreshed resolution metadata/markers.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud