UI element is not clicked when running process though Orchestrator

Hello,

I have an issue where the UI element is not clicked once the process is ran through Orchestrator. I have created a post before about the exact same issue but it was concluded that Internet Explorer was not responding when clicking the download button (UI element is not found when running process though Orchestrator).

We have recently swapped to Chrome and the behaviour remains which got me thinking it is not a browser issue at all. The robot just assumes it clicked on the button but it actually didn’t do anything and carries on with the next activity.

I searched around to see if anyone has found a solution for my case but nothing has really changed anything.

The download button I’m trying to click is very responsive and quick so it’s not a delay issue as even if I do it myself or by running through studio the “Save-As” window shows up immediately.

Thanks,
Marian

Hello @NAyRAM!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

No proper answer for this query yet!. I am facing exactly the same issue.
I working absolutely fine in my machine, but when I run from the orchestrator, the particular UI element is not clicked!.

@Vishnu_Pradhaban

Is your robot installed in service mode?

And did you try using simulate click?

And is the resolution set for your robot in orchestrator?

Cheers