When I click a certain element on the page displayed in Chrome, the screen below appears, and I am constructing a flow to click the date from yesterday (the blue-bordered part as an example).
During execution in Studio or when running a job with the execution environment screen displayed, it clicks the blue-bordered part as expected without any issues. However, for some reason, when executing in the background on the server (running on a virtual machine), it ends up clicking the part outlined in red.
Even with strict selectors, the situation does not change. If there were an error stating that the element could not be found, that would be one thing, but it’s confusing that it ends up selecting a different element instead. If anyone knows a solution, please let me know!
First, to isolate the cause, it might be a good idea to take a screenshot just before clicking the blue frame and confirm if it matches the expected situation.
If there are no issues with that, I think there’s a plan to specify the date with a strict selector using the aaname attribute to avoid clicking on unexpected elements. (If that results in a selector not found error, we can trace the cause from the information about similar selectors in the error message.)
I have the video recording of the relevant workflow enabled in Orchestrator, so I can see what’s happening on the virtual machine, but ideally, the area in the blue frame should become active when it’s clicked, and then it proceeds to the next flow while the area in the red frame is clicked.
The selector for the blue frame is also set to a strict selector, and since the clickable area changes daily, I’ve set a variable for the attributes, specifying the aaname attribute.
At the point you’re trying to click, is the date, which is the intended target for the click, displayed on the screen?
The selector for the blue area is also a strict selector, and since the point to click varies by date, I have set a variable for the attribute, but I have specified the aaname attribute.
The behavior seems a bit odd; for instance, is it possible that the click is happening through some other method that is not a strict selector? Or is there a setting enabled that allows continuation upon an error?
Even though the intended click target is displayed on the screen,
it is not selected, and for some reason, a different element, the red-bordered section, is selected instead.
I checked the properties of the activity that clicks the blue border, and
“Continue on error” is set to OFF.
I had a similar issue before. Since the selector is working correctly in Studio but the click goes to a different location only during unattended execution, I would check the VM’s display scaling/resolution and the Click activity’s Input Mode first.
Try changing the Input Mode from Chromium API to Simulate (or Hardware Events) and make sure the VM scaling is set to 100%.
Also, try using Highlight Element just before the Click. If it highlights the correct date but clicks somewhere else, then it’s probably a coordinate/display issue rather than a selector issue.
Based on your advice, I changed the input mode (input method) to hardware events and executed it, but while the mouse cursor is pointing at the blue frame that I want to click, the red frame is responding instead.
Indeed, when watching the OC video recording, it seems that the screen resolution in the Studio environment is different, so this might be due to the discrepancy in screen resolution.
In this case, where can I make adjustments?
For reference, I will share the property settings for the click in question.
I found out that the resolution can be set in the OC robot settings, and after making that adjustment, the issue was resolved, and it began operating as expected! Thank you very much, Yoichi and Monali_Vekariya, for your guidance!!
Manage tenant - access rights → Click “Edit” at the far right of the relevant user’s row → There is a resolution setting within the enterprise settings, so it might be good to change it here.
