How to set and increase a UiPath robot's screen resolution?

[Lynx (Lnx)]

I have had a great improvement thanks to the advice you gave me, 50% of the process works as I wanted, that is, unattended on a remote server. The problem that I now have and I do not understand the reason, is the following:

Sequence “web1”: works perfectly, The flow is as follows:
-create folders
-goes to the web
-You are logged in
-download files

Sequence “web2”: it doesn’t work, apparently it’s the screen resolution problem or something else:
-create folders
-cannot login.

Important details:

The first sequence I developed in a resolution of 1680 x 1050, then on another pc I worked at a resolution of 1920x 1080 and duplicated the flow to make the second sequence, I did that because it was the same user interface (web), I only changed the url.

The orchestrator error is: “Cannot send input to UI element because it is outside of screen bounds.”

It seems quite strange to me, since practically the sequence “web2” is identical to web1 with different urls, in both cases the web design is identical. Also I test the complete flow on a local machine and everything works ok, but not on the remote server unattended.

For my part, I made sure that the orchestrator is correctly configured the resolution in the robots and also in the uipath.settings file

What other things could I try?

[codemonkee (Tim)]

@Lynx

Cannot send input to UI element because it is outside of screen bounds.

Would need to know more about the specific activity (Properties, configuration, workflow, etc.) that is failing and what it is acting on. My guess there is what @postwick alluded to above #10. Try adjusting your Input Methods.

---

In modern / dynamic UIs I generally don’t find change in resolutions to be that problematic unless of course it is completely removing certain elements when the resolution is too small say for an example a menu bar collapsing into a button. On Legacy Static applications, similar … if the resolution is smaller than the app was designed for you might get a visual cut off of certain elements or container boxes that you cannot scroll which can cause a probably but for me at least generally speaking if the resolution is higher than the app was originally intended for then the number of pixels is still the same and more of a concern when using Computer Visions of sorts.

^^ Last bit is just mostly based on my experience, most of what I have automated against has been ‘legacy’ with a few modern applications here and there, but if they are well designed not going through the UI anyways – for the most part I live in the infrastructure / backend space. You’re mileage may very.