Hello UiPath Team,
I can confirm that I am seeing this error in multiple locations following the latest UiPath update. Please let me know what the fix is for this issue.
Thanks,
Andy
Version: UiPath Assistant 2025.0.167
Error:
Hi @AndyMenon
Yes, many users are facing this error post recent update.
@Hugo_Leonardo_Rodriguez_D @ckshowebay @jjtechteams
Regards
Sonali
Yesterday I logged into Orchestrstor of one of the instances. When I checked one of the machine records it was having a status that said something like “updating in” . I don’t recall the exact message but it was something along those lines.
I don’t know if this is related. But one of the machine templates is marked “Non Comp” .
Andy Menon
Founder, Lead Solution Architect & Engineer | UiPath MVP 2021-25
www.rpavanguard.com | admin@rpavanguard.com
Hi @AndyMenon
It’s most likely due to incompatibility of the robot/ assistant version with the Orchestrator.
Try updating the robot version on the machine.
Hi Ashok,
I will look into it. But I’m trying to understand why an auto update triggered by UiPath is not running to completion?
Why would an update started automatically need to be manually completed?
In the status column of the machine entry in the Orchestrator, a message pops up stating that “the update may take up to 3 hours if the machine is on for the update to run …”.
At least in 2 instances I know that the machine is on for more than 3 to 6 hours.
Just ironic that an automation platform isn’t auto updating to completion. 
Andy Menon
Founder, Lead Solution Architect & Engineer | UiPath MVP 2021-25
www.rpavanguard.com | admin@rpavanguard.com
Last week another update was triggered. After that update, a different error on Assistant bearing error code 401 showed up.
On two machines, i ran into this error. I completely quit Assistant and restarted it.
After that, I haven’t seen any error this entire week.
FYI.