Hi @mikael-andersson91 ,

This problem is not related to the misconfiguration of environment variables.
There are 2 common issues for this error, which we documented on our FAQ page.
If running the agent locally works fine, then most likely the problem is due to setuptools package discovery strategy.
Please note that, if your project contains more than one .py file at root path, setuptools will refuse to create distribution archives to prevent common errors such as accidentally publishing code not meant for distribution (from their documentation).
If that is the case, the easiest fix is to add

[tool.setuptools]
py-modules = []

in your pyproject.toml file.

Thanks for opening this issue, we are currently working on an improvement to surface the underlying environment preparation errors on serverless executions.

I've tried all the proposed solutions here, added the section to my toml file and moved my Python file to a src sub-folder. Same error as before.

Here's a snippet of my project folder:

toml contents:

[project]
name = "my-agent"
version = "0.0.1"
description = "my-agent"
authors = [{ name = "John Doe", email = "[email protected]" }]
dependencies = [
    "uipath-langchain>=0.0.106",
]
requires-python = ">=3.10"

[tool.setuptools]
py-modules = []

And the rest is the exact project from the quickstart guide, with Anthropic usage removed.

@mikael-andersson91 please attach here the NuGet (.nupkg) package.
also, considering the process version 2.4.1-pr-57... I assume you have some sort of github action or similar that is automatically packaging and publishing this agent. If that is the case, may you also share the pipeline .yml file?

my-agent.2.5.1-pr-64-dd42293.nupkg.zip

I've got all of this in a private repository. Adding you temporarily as a collaborator to it.

And as for what is what in there:

• Agent project
• uipath-langchain-pack.yml
• uipath-langchain-deploy.yml
• uipath-langchain-agent-cicd.yml

The last workflow is what is used to combine packing and deployment of the Agent project, used here

Thanks for providing the requested info.

The problem is with the package version created by the github workflow (eg. 2.5.1-pr-64-dd42293)
this is not a valid pyproject version, as it is not compliant with official project specifications.
Thus, the environment preparation step will fail:

To see the environment preparation error logs in cloud, you can now set LOG_LEVEL=TRACE as process env variable.

I get the same error with regular release versions, such as 1.0.0 and 2.0.0

Or wait, I've got a working version now. Seems like the toml and src changes did the trick with a new release version:

my-agent.2.5.2.zip

So I will just have to make sure to make my prerelease versions use a better version convention. Good to know :)

Glad to see this problem solved.
We will work on some Github action templates #101 to avoid similar issues in the future.