Outside of Screen Bounds" errors and element recognition issues on Cloud VMs

Help Cloud Robots
1

Hi everyone,

Since last Friday, we have been experiencing random issues with our Cloud VMs.

The Problem: While running processes unattended, UI elements are suddenly not recognized, or we receive “out of bounds” errors, even though the elements should be visible. The behavior is inconsistent: a process might run fine once, but fail at the exact same step the next time.

When we run these same flows attended on our local machines, they work perfectly as expected.

Error Message:

System exception at initialization: Changes in page layout invalidated anchors geometry. Enable 'IsResponsive' option to fix this issue. at Source: Type Into 'Wachtwoord'

System exception. Cannot send input to UI element because it is outside of screen bounds. at Source: Invoke CreditNext_CreateMemo workflow: Click 'Save and Close'

Environment & Settings:

Resolution: Set to Custom 1920 x 1080
LoginToConsole: We have tested both ‘Yes’ and ‘No’ without success.
Scaling: We checked the VM display settings, but they are grayed out during RDP sessions (standard behavior).
Robot Settings: We have tried both “Custom” and “Use robot local settings” in Orchestrator.

We have already opened a ticket with UiPath Support, but while we wait for their response, we wanted to check if anyone here has encountered similar sudden instability with Cloud VMs recently.

image
image784×779 37.4 KB

2

Try changing the input mode to simulate in Ui-Activities.

3

Does not make a difference. Also on my own development machine it all runs fine.

The problem is not within the automations. It happens randomly on different ones and it tends to fail on different places.

Even when using a library some flows can login to an application where others fail.

4

@DionM

  1. did you check the screenshot or live streaming?is it on right screen?
  2. the first error seems different are you using image based or cv?
  3. second one looks mostly because of resolution only..so simulate or chromium api can help

cheers

5
  1. Yes, all is good. Application is open
  2. None, just the selectors. We try to not use image based and cv
  3. That is not the problem I think because other flows that use the same lib sometimes work fine. Everyhting works fine on my own machine and that one uses the same resolution and packages.
6

@DionM

login to console must be set to no/false

and VM must be signout before running can you ensure these and try to run

cheers

7

Hi, we have tried yes and no but that does not make any difference.

8

Another flow just failed. 5 items are fine, number 6 is all of a sudden out of bounds.

image
image1061×647 78 KB

9

@DionM

in the screenshot same element that failed is visible?

try simulate or chrorium api..may be its rendering differently

latest websites are more dynamic

cheers

10

Cannot see the screenshot but yes, it is vissible as it was for the other 5 transactions.

No, as you can see 5 transactions are fine, number 6 all of a sudden is not. It has nothing to do with the settings in studio, otherwise they would all fail.

11

@DionM

please check the screenshot we never know the changes that might come..I agree it is successful for 5…its not about settings..its about a reliable way to work for all transactions..if its working for few and failing for few then the current setup is not working..so we need to try with ways that work

cheers

12

try recycling UI session every N transaction. Do not run all transactions in one continuous UI session.

  1. Use kill process to kill browser.
  2. Surround specific failing activity with retry scope.
13

The button is visible in the screenshot

But as it worked for 5 transactions then it is not possible for the 6th one to be outside bounds.

14

why would I do that?

15

@DionM

is that some button on excel?

can you elaborate the steps there

if on excel it might be that if the button is appearing only after a click then also you might see the issue

cheers

16

Nop, just in a browser. All errors we have since Friday happen in chrome.

17

@DionM

Try using Mouse Scroll to scroll to the Ui Element you want to interact with first.

18

I have very bad expriences with the mouse scroll. And the element is on screen so no need to do so.

19

@DionM

Try with hover or simulate or chromium api

Cheers

20

As I said that is not the problem. It is not a problem we can fix in studio, it is on the cloud VM’s from UiPath. I also have no clue why onbody from UiPath is responding to this issue.

1 Like