Skip to main content
Question

AA RPA bot performs well when VM window is open, gets stuck and breaks when VM window is closed with no reason.


Forum|alt.badge.img+1

When I try to run the bot with VM window open bot performs all steps as expected, then I try to test it in real life conditions, so I close the VM window, making sure everything is looking clean for the bot and press Run button. 
Bot just gets stuck (doesn’t really matter what step is, it gets stuck at the login screen as well as inside the app not selecting a text box to input data). 

I tried different approaches, adding delays, selecting different type of capture, nothing helps.

Please, help.

6 replies

Stefanie
Most Valuable Pathfinder
Forum|alt.badge.img+5
  • Most Valuable Pathfinder
  • 13 replies
  • April 3, 2025

Hi ​@KyryloR 

we also face this challenge. I guess, if you take a screenshot it will be black when running with closed window.

Our solution is always to have the bot runner VMs connected to a physical machine. We placed this machine in the control center of our data center to make sure no unauthorized persons can access it. If RPA operations needs to access it, they connect remotely.

I hope this helps.


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • 1 reply
  • April 3, 2025

@Stefanie Hello, 

Thank you for your answer. 
Not sure if the approach you mentioned is viable for us, however, I personally would prefer working with a physical computer rather than capturing actions on a remote VM. 

I will try to reach AA support team meanwhile. 

Many thanks,

K


Stefanie
Most Valuable Pathfinder
Forum|alt.badge.img+5
  • Most Valuable Pathfinder
  • 13 replies
  • April 3, 2025

Our developers work on their own VMs. Only production runs on the VMs, that are connected to the machine in the operations center. As we only run unattended bots, normally no one needs to access the bot runner VMs.


zaid.chougle
Forum|alt.badge.img+4
  • Navigator | Tier 3
  • 17 replies
  • April 3, 2025
Stefanie wrote:

Our developers work on their own VMs. Only production runs on the VMs, that are connected to the machine in the operations center. As we only run unattended bots, normally no one needs to access the bot runner VMs.

I would agree to this approach, BotRunner / keep the VM open are the two options where it will work. Another one would be AISense recorder but not sure how much accurate it would be ​@KyryloR, you can try it out

 


balwant.bora
Cadet | Tier 2
Forum|alt.badge.img+3
  • Cadet | Tier 2
  • 7 replies
  • April 4, 2025

Hi,

You can refer to the below KB article.

Black screenshot while running the bot in Unattended mode

Place the batch file in the VM and disconnect as administrator and run the bot without opening the VM, it will work fine.

Batch file to lock/logoff for the runner machine

 

Regards

Balwant Bora


rbkadiyam
Mission Commander | Tier 5
Forum|alt.badge.img+17
  • Mission Commander | Tier 5
  • 587 replies
  • April 4, 2025

@KyryloR  did you verified that in GPU policy ctrl+Alt+Del  enabled ?

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings