Hello world. I am fairly new to the UiPath software and community. Recently took it over at my workplace from a departing employee.
I’ve seen similar questions asked previously, but none exactly fit what my issue is. UiPath seems to be having trouble identifying elements in a 3rd party software. I blame the other software more than anything. For the sake of this, I’m just attempting to log in. The catch is that it works fine when I hit the run button. But I saved and published my bot, used the latest version in Orchestrator and scheduled it, and it fails to identify the element. Here is the entire output from the logs provided in Orchestrator:
Job failed. Reason: Cannot find the UI element corresponding to this selector: <wnd aaname='System' app='obunity.exe' cls='HwndWrapper*' title='Login' /><ctrl idx='1' role='graphic' /> An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: UiPath.Core.SelectorNotFoundException: Cannot find the UI element corresponding to this selector: <wnd aaname='System' app='obunity.exe' cls='HwndWrapper*' title='Login' /><ctrl idx='1' role='graphic' /> ----> System.Runtime.InteropServices.COMException: Cannot find the UI element corresponding to this selector: <wnd aaname='System' app='obunity.exe' cls='HwndWrapper*' title='Login' /><ctrl idx='1' role='graphic' /> at UiPath.UiNodeClass.FindFirst(UiFindScope scope, String nodeID) at UiPath.Core.UiElement.FindFirst(FindScope scope, Selector selector, IVariableResolver resolver) --- End of inner ExceptionDetail stack trace --- at UiPath.Core.Activities.TaskAsyncCodeActivity
1.EndExecute(AsyncCodeActivityContext context, IAsyncResult result) at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result) at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)`
This appears to be the selector that fails:
<wnd aaname='System' app='obunity.exe' cls='HwndWrapper*' title='Login' /> <ctrl automationid='userNameTextBox' />
The above validates properly when the window is open. After a (failed) run on Orchestrator, I connect back to the machine and see that the application obunity.exe is open and ready to be used. If I run the process again while watching it, it works just fine.
Any help is greatly appreciated here. Been plugging away at this all day trying to figure it out. Assuming just a newbie mistake. Happy to provide any additional info if needed.
Best,
Xander