First type into - works great even when i dissconnect RDP connection
Second type into - robot stop on that activity and do not type anything. When i connect to RDP it starts to type immediately
So i have the same properties in both activities. One works when RDP is disconnected, and another one not. This is the same aplication. Please advise what can be done here? We do not have Orchestrator.
I have created while loop based on get text activity.
while: get text from field is empty - > type into → send mail with get text variable
So bot is working when disconnected im receiveing blank mails -> because type into not working. Once i connect again to RDP -> its is starting to type in the field → i receive mail with my input string.
We should have any on going connections with the VM(bot machine) like user logins. to avoid this we have to restart the VM to make sure that no user logged into this VM machine.
Have you installed the Bot which you are running as un attended from orchestrator by using MSI installer since we must install the bot with service mode since service mode bot is required for un attended automation.
I mean i tried modifying all properties on not working one, trying SimulateType, SendWindowMessages like everything, does not matter. If im dissconnected from RDP it wont type. If i connect it is typing. Basicly have no idea why the first one is able to work and another one not.
Guys, the solution were changing robot to another PC with license. No change in robot at all, on one it was not working and another PC it is without problems - i dont know what kind of solution it is, and what exactly fix it.