I am having an interesting issue, and I am hoping someone may offer some insight or a possible solution?
I have a process that succeeds 100% of the time when i run it locally, 100% of the time when i run it on the server manually, 100% of the time when i run it as a job through Orchestrator MANUALLY, but only maybe 50% of the time when i run it through Orchestrator as a SCHEDULED JOB.
It is a job that opens up Internet Explorer, navigates to a website, logs in, inputs data, updates data, saves data, loops through a list of users to update, then exits, logs out and closes the browser. The job seems to always fail on the “exiting” process (this is when it is backing out of web pages to get to the root directory). But it fails at different points of this process, and with a few different errors.
Again, this same process runs 100% successfully in every way EXCEPT when Scheduled through Orchestrator, and even then it succeeds some times but not in others. I’m not sure the exact error message it throws matters, but here are the 2 common errors that it throws:
An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
UiPath.Core.InvalidUiElementException: The UiElement is no longer valid ---->
System.Runtime.InteropServices.COMException: Invalid UI node.
- Process: SigUIUpdateCCNs
- Environment: Test Environment
- Robot: Test Robot 1
- Machine name: RLTIUIPHTS1
- Info: Cannot find the UI element corresponding to this selector: