Airgapped Automation Suite environments (deployments without internet access) require special configuration for Python package dependencies. You need to configure your project to use a Python package feed that is accessible within your environment.
+You have two main options for managing Python packages:
+Azure DevOps Artifacts can serve as a private Python package feed that includes packages from common public sources (PyPI). This is suitable for environments with restricted internet access where Azure DevOps services are still accessible.
+You'll need to create a Personal Access Token (PAT) to authenticate with your Azure DevOps feed.
+Add the following configuration to your pyproject.toml file:
[[tool.uv.index]]
+name = "my-feed"
+url = "https://az:PAT_STRING@YOUR_ORG.pkgs.visualstudio.com/YourProject/_packaging/my-feed/pypi/simple/"
+publish-url = "https://az:PAT_STRING@YOUR_ORG.pkgs.visualstudio.com/YourProject/_packaging/my-feed/pypi/upload/"
+default = true
+Replace the following placeholders:
+PAT_STRING: Your actual Personal Access Token from Step 2YOUR_ORG: Your Azure DevOps organization nameYourProject: Your Azure DevOps project namemy-feed: The name of your feed (in both the name field and the URL)Tip
+Organization-scoped feeds: If you're using an organization-scoped feed instead of a project-scoped feed, the URL format will be slightly different, but the same authentication logic applies. The URL will follow this pattern:
+ +Note the absence of the project name in the URL path.
+Tip
+Using environment variables: You can also configure the feed URL using environment variables instead of hardcoding the PAT in pyproject.toml:
[[tool.uv.index]]
+name = "my-feed"
+url = "https://az:${AZURE_DEVOPS_PAT}@YOUR_ORG.pkgs.visualstudio.com/YourProject/_packaging/my-feed/pypi/simple/"
+default = true # to use this feed as your default
+Then set the environment variable before running your commands locally:
+ +Important: When deploying your process to UiPath, you'll need to configure these environment variables in the process settings. Navigate to your process in UiPath Orchestrator and add the environment variables (e.g., AZURE_DEVOPS_PAT) with their corresponding values. This ensures your process can authenticate with the external feed when running in the UiPath environment.
Tip
+Specifying sources for specific packages: If you don't want to set your custom feed as the default, you can use [tool.uv.sources] to specify which packages should come from your custom feed:
[[tool.uv.index]]
+name = "my-feed"
+url = "https://az:PAT_STRING@YOUR_ORG.pkgs.visualstudio.com/YourProject/_packaging/my-feed/pypi/simple/"
+
+[tool.uv.sources]
+uipath = { index = "my-feed" }
+# Add other packages as needed
+some-private-package = { index = "my-feed" }
+This allows you to selectively pull specific packages from your custom feed while using the default PyPI for others.
+Once configured, you can install dependencies using uv:
To verify your feed configuration is working correctly, you can check that uv resolves packages from your custom feed:
For truly airgapped deployments where you need complete control over your infrastructure, you can host your own Python package index within your network. This approach eliminates any external dependencies and provides full control over the packages available in your environment.
+Several tools are available for hosting a Python package index:
+Once you have your Python package index set up and accessible within your airgapped network, configure your pyproject.toml to point to it:
[[tool.uv.index]]
+name = "internal-pypi"
+url = "https://pypi.internal.company.com/simple/"
+default = true
+If your internal index requires authentication:
+ + + + + + + + + + + + + + +Install Python ≥ 3.11:
+Alternative: mise
+Install uv: + Follow the official installation instructions for your operating system.
+Create a virtual environment in the current working directory: +
+Activate the virtual environment:
+Install dependencies: +
+For additional commands related to linting, formatting, and building, run just --list.
Create a project directory: +
+Initialize the Python project: +
+Set the SDK path: +
+Install the SDK in editable mode: +
+++Note: Instead of cloning the project into
+.venv/lib/python3.11/site-packages/uipath, this mode creates a file named_uipath.pthinside.venv/lib/python3.11/site-packages. This file contains the value ofPATH_TO_SDK, which is added tosys.path—the list of directories where Python searches for packages. To view the entries, runpython -c 'import sys; print(sys.path)'.
key instead of id for resource identifiers# type: ignore comments unless absolutely required.# type: ignore at the start of a file.retrievekey instead of id)retrieve_by_[field_name] (for fields other than key)listcreateupdatedev build, please add a build:dev label to your PR.dev version from the PR description/comments to use as needed {
+ "Code": "Serverless.PythonCodedAgent.PrepareEnvironmentError",
+ "Title": "Failed to prepare environment",
+ "Detail": "An error occurred while installing the package dependencies. Please try again. If the error persists, please contact support.",
+ "Category": "System",
+ "Status": null
+}
+
+
Example of the error as it appears in UiPath Cloud Platform
+This error might occur when deploying coded functions or coded agents to UiPath Cloud Platform, even though the same project might work correctly in your local environment. The issue is often related to how Python packages are discovered and distributed during the cloud deployment process.
+src layout)project_root/
+├── src/
+│ └── your_package/
+│ ├── __init__.py
+│ └── your_modules.py
+├── pyproject.toml
+└── setup.cfg/setup.py
+If you need to maintain your current project structure, you can configure custom package discovery in your pyproject.toml:
pyproject.tomlFor more detailed information about package discovery and configuration, refer to the official setuptools documentation.
+The UiPath CLI automatically works with your corporate network setup, including proxy servers and security tools like ZScaler, by leveraging your system's native SSL certificate store.
+Configure these environment variables to route CLI traffic through your corporate proxy:
+Tip
+For IT Administrators: Add these environment variables to your Group Policy or system configuration:
+ +Warning
+The CLI uses a local HTTP server for the authentication callback. You must exclude localhost from your proxy using NO_PROXY=localhost,127.0.0.1 or authentication will fail.
The UiPath CLI automatically uses your system's certificate store (Windows Certificate Store, macOS Keychain, Linux ca-certificates). Corporate certificates installed via Group Policy or IT tools will be automatically recognized.
+If you encounter SSL certificate errors:
+You may see errors like these in the logs panel:
+[Error] .venv/lib/python3.14/site-packages/azure/monitor/opentelemetry/exporter/export/_base.py:472: SyntaxWarning: 'return' in a 'finally' block
+[Error] return ExportResult.FAILED_NOT_RETRYABLE # pylint: disable=W0134
+[Error] .venv/lib/python3.14/site-packages/azure/monitor/opentelemetry/exporter/export/_base.py:474: SyntaxWarning: 'return' in a 'finally' block
+[Error] return result # pylint: disable=W0134
+If your Python job runs are hanging or not completing when deployed to UiPath Cloud Platform's serverless environment, this may be caused by a library incompatibility issue from an outdated version of the UiPath Python library.
+Ensure you're using uipath version 2.1.169 or later. This version includes fixes for serverless execution.
To check your current version:
+To upgrade to the latest version:
+After upgrading, update your pyproject.toml to ensure the correct version is used in your deployment:
pyproject.toml: +
+Note: This FAQ will be updated as new information becomes available. If you continue experiencing issues after following these solutions, please contact UiPath support.
+ + + + + + + + + + + + + +