You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
uipath init: every run writes new uniqueId values to entry-points.json, so an unchanged entry point gets a new identity #2011
Short version: Each uipath init (uip codedagent init, uip function init) generates a fresh uuid4 for every entry point, so a second run on an unchanged project changes entry-points.json. The id is copied into the solution's process resource spec (entryPointUniqueId) by uip solution resources refresh and by pack, so each run also rewrites the solution's resource file. init should keep the id of an entry point that already exists in entry-points.json.
Evidence
Versions: uipath 2.15.5, uipath-langchain as installed with it, uip 1.208.0-dev.10025.
A Python function project (uip function new -l py, uip function init), then uip function init again. The only change in entry-points.json:
A LangGraph agent, uip codedagent init twice: the same one-line change (output/entry-points-diff.txt). bindings.json is byte-identical between the runs and holds no entry-point id.
In a solution, uip solution resources refresh writes the id into resources/solution_folder/process/function/<project>.json as spec.entryPointUniqueId (and inside the embedded entryPoints string). After a further init that file differs from the project; the next refresh reports ReconciledSpecs: 1 and rewrites it. uip solution pack refreshes the resource files first, so a package carries the new id: every init changes the entry point's identity in the project and in the solution, with no change to the code.
Code path
UiPath/uipath-pythonpackages/uipath/src/uipath/_cli/cli_init.py:184-209 (bbd3f2b), write_entry_points_file: dumps the schemas the runtime factory returned, with no read of the existing file.
uipath/functions/runtime.py:289 and uipath_langchain/runtime/runtime.py:326: uniqueId=str(uuid.uuid4()) on every schema build.
Fix
In write_entry_points_file, read the existing entry-points.json and reuse the uniqueId of the entry point with the same filePath; this covers every framework in one place.
Or derive the id deterministically from the project id and the entry point's file path.
Activity