I have two development environments, one with Orchestrator and the other without. When I opened what I developed on the Orchestrator side in the environment without Orchestrator, I received an error saying that certain activities do not exist. Upon investigating the cause, I realized that the package versions are quite different.
The attached image is from the environment with Orchestrator. The environment without Orchestrator does not have such high versions like 2.4.xx or 24.xxx.
I asked Gemini about this, and they suggested that I might be using a pre-release version. However, when I checked the box for “Include pre-releases,” even higher versions appeared, so it seems that I am indeed using officially released versions.
The UiPath versions in both environments are the same (Studio 2024.10.16). How is it possible that the downloadable package versions are different? Additionally, I created this in the environment with Orchestrator, but the actual execution environment is without Orchestrator. In this case, will I need to downgrade and recreate it? (´;ω;｀)
At the beginning of the scenario, I am using “UiPath.Web.Activities.Http.NetHttpRequest (HTTP Request),” but it seems that this activity does not exist in older versions…
It’s quite possible the activity is deprecated in latest version of the package.
Do you know which activity which is showing does not exist? if yes, we can find the package version it’s released and install that version of the package. If no, it will be hard to find which activity is missing. In that case check what logic that activity was accommodating.
Is the environment without Orchestrator a closed network environment? If it can connect to the internet, missing packages can be automatically downloaded from the feed online, but I don’t think that’s happening.
For now, the easiest solution would be to copy the contents of the c:\Users\[UserName]\.nuget\packages
folder from the machine connected to Orchestrator to the same folder on the machine without Orchestrator. This should resolve the issue. (In some cases, you may need to copy a few .nupkg files.)
If you want to prevent this issue in the future, you can create a project using the version of the activity packages bundled in 24.10.16. (Since the default is this version, I think it would either be that you explicitly upgraded or that you used such a template.)
It’s quite a hassle to have to place each .nupkg in the execution environment, and it seems like it’s not even the recommended version, so I’ll recreate the project using the activity package bundled with version 24.10.16 instead.
