I am using UiPath Community Edition. Processes were working fine before the 2025.0.166 STS update. These processes work fine when run from studio but fail when run from assistant via triggers. They give “Could not find the user-interface (UI) element for this action”. I tried updating to latest package versions, deploying new build but no use.
Note: processes are working fine when run from studio.
Welcome to the community
Cheers
I am running the studio in same machine. I am having no issues in running studio but the package build of same process fails. I was having same issue with one element but when I removed computer vision from that element, unattended process detected it. Now am getting same error for another ui element in unattended run.
Check if the UI selectors are reliable and concrete to work in dev and prod as well.
Try to use simulate input method wherever possible as it
simply disconnecting and reconnecting using client id and client secret resolved the issue, allowing the processes to start successfully—this approach usually fixes similar connection or authentication problems.
If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath
Hey @sanket.nawaghare many of the fellow member are facing that type of problem.as per the solution is go to orchestrator remove the machine and add that same machine again that it will generate client ID and client Secret copy that and paste it to the assistant where are you running your unattended bot. now your are good to go to run your process again. and before doing that if this happen in type into or any ui activity kindly enable the simulate/send window from the property panel of that activity.
cheers
Thanks for the suggestions I will try them
Thanks @singh_sumit this solution worked. Thank you all for helping me with this issue.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.