When I deployed the work flow to Orchestrator. it showed the following message:
message: Retry Scope: Could not find the user-interface (UI) element for this action. Possible solutions: • Ensure application is opened and the UI element is visible on the screen at execution time • Edit the Target of the UI activity and use Validation to debug the issue. • If needed, re-indicate the element as its properties might have changed • Use “Check state” activity to check the application state before executing the action • Increase the “Delay before” value to allow time to the application to render entirely and become responsive
I am sure the user of sever was logged off when trigger is on.
And the daily process of RPA is running in the machine, that’s why that i think the resolution is ok.
Thank you for your reply.
I cannot edit the setting as i am not administrator.
Is there any other possible issue cause this error. Such as any activities?
To isolate cause, can you try to take screenshot (or video) when error occurs? we can use feature of Orchestrator or TakeScreenshot activity in the workflow.
Just to confirm is this the first ui activity in the process?
If not check the selector of this activity and also it might be possible that the previous activity did not execute fully or properly and it dis not come to this page at all
Depending on the type of bot you might have a lag in application. You can use Wait for page load to Complete and it’ll wait for the element to be visible.
@Anil_G
I remove Activity-Password.
For Wait for download, I found it cannot be used in Orchestrator, Do you have another suggestion to monitor the download folder and move it to specific folder.
For Wait for download, I found it cannot be used in Orchestrator
Yes it can.
First off, Orchestrator isn’t where your automations are running. What you are doing is running the job unattended. Orchestrators tells the robot.exe process on a server to start a job. The job runs in a RDP session on that server.
Log into the server via RDP using the same account you’re trying to run the job with. Then SIGN OUT from the start menu - don’t just close the RDP window. Now try running the job.
If that doesn’t work, make sure you have installed robot on the server in service mode, NOT user mode.
The error message doesn’t indicate this, because the error comes from the Retry Scope not the faulted activity. I suggest removing the Retry Scope so that you will know exactly which activity is faulting.
