Our Prod robot doesn’t update to the latest version, it is currently running on version 25.10.16 while the latest version is 25.10.17
If your Prod Robot is still on 25.10.16 while 25.10.17 is available, first check the Auto Update policy for that machine in Orchestrator.
For an unattended Production Robot:
- Go to Tenant → Machines.
- Select the Production machine → Edit → Maintenance.
- Check Auto Update.
- Set it to Latest version if you want it to receive 25.10.17.
- Check the Version status. If it shows Non-compliant or Update failed, check the update logs.
UiPath’s Update Service normally checks for updates and installs them when the Robot is idle. UiPath Documentation+1
Could you please confirm whether Robot auto-update is enabled for this machine/tenant? If auto-update is configured, we would expect the Robot to upgrade automatically; otherwise, a manual upgrade may be required.
Happy Automation
Hi @darrel.rathelele ,
If your Production Robot is still on version 25.10.16 while 25.10.17 is available, check the following:
- Verify that auto-update is enabled in Orchestrator/Automation Cloud.
- Confirm the robot machine can reach the UiPath update server and there are no proxy/firewall restrictions.
- In Orchestrator, ensure the Machine Policy/Update Ring is assigned to the robot and includes version 25.10.17.
- Restart the UiPath Robot Service or reboot the machine and check for updates again.
- Review Robot and Event Viewer logs for any update-related errors.
- If the update still does not install, download the 25.10.17 installer and perform a manual upgrade.
Thanks
Please check whether automatic updates are enabled for your Production Robot.
Also verify:
-
The Robot machine has internet access to UiPath update services.
-
No firewall or proxy is blocking the update.
-
The UiPath Robot Service is running properly.
-
The update channel configured for the Production environment is correct.
You can also restart the Robot machine/UiPath Robot Service and check again.
If it still remains on 25.10.16, please share whether you are using Automation Cloud or Automation Suite and how the Robot was installed (MSI or other method). This will help identify the exact cause.