My Automation Cloud tenant is on the Community Plan. My macOS UiPath Assistant version is 26.0.197-cloud.24027, while Orchestrator reports it requires 26.0.197-cloud.240270. The auto-update policy is Latest version, but my workspace machine remains Non compliant and Studio Web cannot start “Indicate on local machine”. Assistant is signed in to the same organization. How can I obtain the matching macOS build or refresh the rollout?
Yes, the screenshot confirms the installed UiPath Assistant version is:
2026.0.197 (26.0.197-cloud.24027)
So the issue is likely the build/revision mismatch mentioned in the forum post, where Orchestrator expects 26.0.197-cloud.240270.
You can point out that the Assistant is already on the correct 2026.0.197 release, but the reported build suffix differs. This supports checking the tenant’s machine compliance/update rollout rather than simply reinstalling a completely different major version.
Thank you. Is there any way for a Community user to force a refresh/check for the required build 26.0.197-cloud.240270 on macOS, or can UiPath reset the update/compliance state for my tenant? The policy is already Latest version, and the Assistant has remained open and connected.
Hey @yi044, if Studio Web cannot be indicated locally and the machine is non-compliant, you would first check the Assistant/Robot version against the Orchestrator Machine Template. A version or build mismatch can cause non-compliance, so you would synchronise the versions and reconnect the local machine.