Hello guys, I cannot upgrade my project in orchestrator after i changed my code.
Hi @Gokul_Murali
If you made changes to your UiPath project and cannot upgrade it in Orchestrator, it could be due to several reasons. Here are a few things you can check:
-
Make sure you are uploading the correct version of the package. If you have multiple versions of the package, ensure that you are uploading the latest version with the changes you made.
-
Check if the package is already installed in the environment. If the package is already installed in the environment, you may need to uninstall the existing package before upgrading it to the new version.
-
Ensure that you have the necessary permissions to upload the package in Orchestrator. If you don’t have the necessary permissions, you may not be able to upgrade the package.
-
Check if there are any errors in the package. If there are any errors in the package, you may not be able to upgrade it. Check the logs to identify any errors and fix them before uploading the package again.
-
Ensure that you are uploading the package to the correct environment. If you have multiple environments in Orchestrator, ensure that you are uploading the package to the correct environment.
I hope this helps you resolve your issue.
I have uploaded the correct version of the package and verified with the help of project Json file.
The new package was not installed because the old project version was different with the newly updated project version.
I have all the permission to upload the package in orchestrator.
There is no error in the package since i try to upload the other package also i didn’t get any option to upgrade.
iam not getting any error.
I made changes to the process try to republish.
Previously i have an upgrade option after republish, but now there is no option.
There are 3 process in the same environment i have tried other 2 also, same issue (No upgrade option)
This could be because the version number in the project JSON file was not updated to match the version number of the new package.
To resolve this issue, you need to make sure that the version number in the project JSON file is updated to match the version number of the new package. You can do this by opening the project JSON file and updating the version number.
Once you have updated the version number, you can upload the new package to Orchestrator and it should install correctly.
If you still encounter issues with upgrading the package, you may need to check the package dependencies and ensure that they are compatible with the new version of the package you are trying to upload. Additionally, you may need to check the settings in Orchestrator to ensure that the package versioning is set up correctly.
Did you change the name in the project.jaon?
If not …that means the project is getting published as new version under the previous package name itself
Can you please check the same
Cheers
This is the project version
Publishing from Studio to orch
This is the orchestrator after publish
Before if i publish ill get an icon to upgrade not its not
Are you checking the correct Orchestrator?
Can you check which Orchestrator it is connected to
cheers
YES THIS IS THE CORRECT ORCHESTRATOR AND THE ORCHESTRATOR IS CONNECTED
@Anil_G THERE IS ONLY ONE ORCHSTRATOR ALL THE PROCESS ARE PUBLICHED TO THAT ORCHETRATOR AND IT IS CONNECT to robot.
Can you check the name in the project.json and did you migrate form classic to modern?
And as you are not getting error also it should have been published…once you publish are you getting a response that the project is published?
Cheers
Yes iam getting a popup that project published successfully.
migrate form classic to modern? (Can you mention how can i de that)
Hello!
I’m having the same problem, were you able to solve it?
Hello Amanda,
I have the same issue like this.
I have already a process in orchestrator so when i try to republish the modified code it is having issue.
What i found is that the process name which is already in orchestrator and the process which i try to republish have diffrent name thats is the issue in my case
So i changed the process name in json for the modified process as same as the process in orchestrator which is published earlier
Check whether process name is correct in the json file