Today the studio and assistant program was updated to version 2025.0.166 and the unattended robot that was operating normally after that update generated an error stating:
Couldn’t install the ‘rpatest’ package UiPath.CoreIpc.RemoteException: Couldn’t install the ‘rpatest’ package —> UiPath.CoreIpc.RemoteException: NU1101: Unable to find package rpatest. No packages exist with this id in source(s): Processes Feed. PackageSourceMapping is enabled, the following source(s) were not considered: Connect, Local, nuget.org, Official, Orchestrator Host. ‘Client ID or client secret is incorrect.’ exception on
after updating might be the unattended robot could not install the rpatest package because package source mapping limited access to the processes feed where the package was not found, and an authentication issue was indicated by the client id or client secret is incorrect message.
Pls try to , re-publish the rpatest package to the processes feed, check the package source mapping settings in orchestrator to ensure the correct feed is included, verify the unattended robot’s machine key and credentials, and confirm it has the right access to the process and environment in orchestrator.
If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath
Hey @rpa40 generally in the production we use the Stable version of Studio and as well as Assistant. because in the latest version there might be some bug or any activity related issue occur which cause the process.so only work with stable version.
can you open that same project in the studio and Republish it.if any small error or any package related issue come you can fix that and then publish it to orchestrator and then add find your package and add into the process. and one more thing .
before changing that try to run your newly published package if still error comes then There is also machine key and credentials related issue message also shown-
so if you change the machine credentials or machine key is expired or changed delete the previous machine and add that same machine with the credentials.
Hello, I do have the same problem here. Robot is updated to that version, and for every aunattended automation I am executing from orchestrator the error message is shown (same as in OPs post but with different packages obv.) Is this a bug? Running community version btw
Thank you all so much for taking the time and helping me, I did everything I was told and the @AceV solution worked for me.
From the orchestrator I deleted the machine that I had created for the execution of the unattended robot, then I recreated the machine, then I started with the new ID and secret to UiPath Assistant and the robot was executed correctly it no longer generated the error.
