An exception occured Could not find the user-interface (UI) element for this action - unattended bot is unable to interact with the application

Help Orchestrator
,
1

My unattended bot has problem to run from the orchestrator, get the error “An exception occured Could not find the user-interface (UI) element for this action.”. It worked before but stopped working recently. The bot runs fine if the remote connection to the bot is on. Thanks advance for any comment.

2

Hi @Hu_Xiaotao

Go to Tenant → Manage Access → Assign Roles → Robot Accounts → Click on three dots and click on Edit → you will find Robot Settings → Enable Login to Console by keeping option as No → Click Update.

This should help you run the bot, even when your Remote Connection is locked.

image
image1112×877 37 KB

Hope it help!!

3

Thanks for the suggestion. It still doesn’t work once I close the remote bot.

4

Hi @Hu_Xiaotao

Are you working with desktop application?

Regards

5

This means you installed UiPath Robot on that server in user mode instead of service mode.

6

No, I’m working with a web app.

7

Hi Paul,

The bot is service mode and the process worked before. Not sure what happened recently, it stopped working.

8

Someone probably logged into the server then just closed the RDP window, leaving the session active. Log in as the bot account then sign out, don’t just close the RDP window.

9

I replaced the first action clicking the Search button with pressing the Enter key and the problem goes away, not sure why suddenly the button doesn’t work in the Unattended bot.

10

I told you a possible reason why. Did you try the solution I gave you?

11

Yes Paul, I tried " closed the RDP window, leaving the session active. Log in as the bot account then sign out, don’t just close the RDP window." but it didn’t work. After I replaced the Search button, it started working again. It seemed only that single UI caused the problem.

12

Sounds like the page changed and your selector was no longer valid. Show me your selector, there are often things UiPath gives you by default that aren’t good properties to use like css-selector.

13

The weird thing is that the Search button works fine if running the bot with the RDP connection is on.

14

Again, that points to an issue of either Robot being installed in user mode not service mode, or someone closing the RDP window without signing out. Did you log in as the same user the job is running under and then sign out, then run the job?

15

yes, I always signed in as the same user. After using the Enter key instead of the Search button, even without manually sign out the bot will automatically take the server and runs very well.

16

You should not be running unattended automations that way. You should not have to. Sending a keyboard shortcut isn’t UI automation, so that’s why it hides the problem.

17

The enter key isn’t used alone, it’s combined within the Type Into activity. We usually run the bot directly from the orchestrator.

18

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.