Skip to content

fix: support process entry point selection (#1508) - #1824

Open
radu-mocanu wants to merge 1 commit into
mainfrom
fix/issue-1508-process-entry-point
Open

radu-mocanu wants to merge 1 commit into
mainfrom
fix/issue-1508-process-entry-point

Conversation

@radu-mocanu

@radu-mocanu radu-mocanu commented Jul 22, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • add an explicit entry_point argument to synchronous and asynchronous process invocation
  • forward the selected entry point as EntryPointPath in the Orchestrator StartJobs payload
  • cover both invocation paths and bump the uipath-platform patch version with dependent lockfiles

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

  • uv run --no-sync pytest tests/services/test_processes_service.py (9 passed)
  • uv run --no-sync pytest (1590 passed, 7 skipped, 4 deselected)
  • uv run --no-sync ruff check .
  • uv run --no-sync ruff format --check .
  • uv run --no-sync mypy src tests
  • git diff --check

Copilot AI review requested due to automatic review settings July 22, 2026 07:50
@github-actions github-actions Bot added test:uipath-langchain Triggers tests in the uipath-langchain-python repository test:uipath-integrations labels Jul 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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] = None to sync/async process invocation APIs in ProcessesService.
  • Include EntryPointPath in the generated StartJobs payload when entry_point is provided.
  • Update service tests to cover both sync and async invocation with an explicit entry point; bump uipath-platform patch 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.

@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:uipath-integrations test:uipath-langchain Triggers tests in the uipath-langchain-python repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants