Virtual Click False Is Different On 2 Different Robots With Same Resolution

Hello,

I have 2 separate robots (computers) each with the same resolution doing a task through Chrome that requires clicking on a button using Virtual Click = false. On the robot that I recorded the workflow on, this works fine. On the other robot, the click is off by about 100 pixels. If I record the interaction again on the other robot, it will work there but not the first one.

I have taken screenshots and measured the resolution on each and everything seems to be correct and in the same spot. Any thoughts on what might be causing this? Is there some setting that I may have different?

Hard to say what is happening without seeing the Workflow depends on what the recorder recorded. But my bet is that its tied to screensize/resolution.

1 Like

That was my thought too. I played around with some of the RDP settings to make sure each one had the same hard coded resolution. I just finished a test where I had the robot right click on the element and then take a screenshot. Both were identical. Currently waiting on an item to come in that needs to be processed so I can see if it starts working.

Check if you have changed DPI ( zoom ) ( see screenshot from windows 10 here )

I confirmed the zoom setting is the same for both. If it makes a difference, these are windows 11 machines.

I also see that clicking inside of iframes is a potential known issue. Could this be the reason it works on one and not the other? The button I am trying to click does reside inside of an iframe with a frameset.

I was able to figure this out and it is related to the bug reported in this post which has been fixed in a newer version. One robot was attempting to click the wrong element because we were using the internal index value from an NMGetElement call that iterated through several items.

1 Like

Nice, glad you found the solution

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