What should be the input mode of click activity for web automation in unattended mode

Help Automation Suite
, ,
1

I am automating a web application from edge where I have to click on some buttons. I used use browser modern activity and inside it in click activity I used input mode as hardware events. It was working fine and fast when I run it from studio. But when I deploy the process and run as unattended from orchestrator inside a vm , it is executing very slow like it is taking 1 minute nearly. The same activity in attended mode executed within 5 minutes during the development. Also when I open the vm and run it from orchestrator it is executing fast but once I close the vm and run complete unattended it is slow. Do I need to change the input mode of click activity from hardware events to simulate or chromium API?

2

hi, @mohamedalthaf Try changing your Click activity input mode from “Hardware Events” to either “Simulate” or “Chromium API” for faster and more reliable execution

3

Thanks when I run it in unattended mode inside locked vm environment will it execute fast similar to attended environment because in attended mode I kept hardware events it was working fast but in unattended mode only it is slow. Is there any screen resolution or anything that are connected with hardware events

4

In a locked VM hardware events it run slowly because they depend on screen visibility and resolution…Switching to Simulate or Chromium API input modes ensures fast reliable execution in unattended locked environments as these modes work in the background without needing the screen to be active.

5

@mohamedalthaf

first try to include log messages and check which activities are taking time

ideally runtime should be faster unless there are other load delays..can check live streaming or recording as well

cheers

6

Hi @Anil_G. Recordings and streamings are disabled in my organisation. In other workflows I used same as browser input modes for click activities. The browsers has chromium API mode. They are executing fast. But in this particular workflow I used hardware events for click activity and it is slow. So want to confirm if this is related to input mode

7

@mohamedalthaf

it can be as well

please look at logs and see before and after activity timestamp differences

cheers