fix: support process entry point selection (#1508)#1824
Open
radu-mocanu wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes multi-entry-point process invocation by introducing an explicit entry_point argument on ProcessesService.invoke() / invoke_async() and forwarding it to Orchestrator’s StartJobs payload as EntryPointPath, enabling callers to select a non-default entry point while preserving the existing fire-and-forget behavior.
Changes:
- Add
entry_point: Optional[str] = Noneto sync/async process invocation APIs inProcessesService. - Include
EntryPointPathin the generated StartJobs payload whenentry_pointis provided. - Update service tests to cover both sync and async invocation with an explicit entry point; bump
uipath-platformpatch version and lockfiles.
Reviewed changes
Copilot reviewed 3 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/uipath/uv.lock | Bumps locked uipath-platform version used by the main uipath package. |
| packages/uipath-platform/uv.lock | Updates the platform package lockfile for the new patch version. |
| packages/uipath-platform/tests/services/test_processes_service.py | Extends invoke/invoke_async tests to assert EntryPointPath is sent when requested. |
| packages/uipath-platform/src/uipath/platform/orchestrator/_processes_service.py | Adds entry_point parameter and forwards it into the StartJobs payload as EntryPointPath. |
| packages/uipath-platform/pyproject.toml | Bumps uipath-platform version from 0.2.12 to 0.2.13. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Why
Multi-entry-point packages currently always run their default entry point because ProcessesService drops the requested path. This keeps the existing fire-and-forget behavior while allowing callers to select the intended entry point.
Addresses part of #1508
Validation