Robotic Process Automation (RPA)

Hi Larissa,

Since this only happens for scheduled runs, my guess here is that you might be facing an issue caused by the runtime not being able to unlock the machine. I suggest you double-check the configurations to ensure the bot is configured to unlock the machine when running; otherwise, any commands that interact with the screen might fail. Try configuring a user credential for the computer that is being used. The Managing computers documentation page has more information.

I don’t think the problem is related to unlocking the machine. I’m using the screen recording feature, so I was able to check exactly what happens during the scheduled run: the machine does unlock successfully, SAP opens, the transaction is accessed, but when the bot tries to fill in the fields, it fails.

So it looks like the bot is not able to focus on the SAP window at that moment, even though it is already open and accessible. 

If you are connecting to the bot's user using Remote Desktop, you need to disconnect from the session using AlwaysOn, so that the user session goes to the computer's console session.

When Windows does not recognize that the session as visual, it does not render anything, which means that no app windows will be visible.

You can confirm this by using the printScreen command, which should generate a completely black image, precisely because the session the robot is using is not visual.

I added the printScreen command and executed it during the scheduled run; the image wasn’t black, it captured the SAP screen normally.

weird.. do you have the logs at INFO level?

Right after the SAP window starts and the transaction is opened, I added a mouseClick command on the center of the screen. After that, the automation started working.
Before, I was only using focusWindow, but apparently it wasn’t actually focusing the SAP window. With the mouse click, the window gets focus and the bot can interact normally.