https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86286#M37160 Are you accessing the resource machine via RDP (mstsc)? RDP is not a suitable access tool and is specifically not recommended by BP. The reason RDP doesn't work with surface automation is that the remote desktop only exists when you have the window open, and is destroyed once the window is closed. After closing the window BP is still running on the remote machine, but there is no UI, so any process that requires the UI (global click, keystroke, screenshot, SA) will encounter problems. You can test this by running a process that captures a screenshot - when the window is closed the screenshot will be black. One solution is to use a remote access tool where the target machine persists, and is unaffected by you viewing it (see link above). Another solution is to use Login Agent to log in and to run the process unattended. And if you do connect via RDP, you must run the Log Out and Log In processes to reinstate the remote desktop. Mon, 14 May 2018 13:11:00 GMT John__Carter 2018-05-14T13:11:00Z https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86284#M37158 Hi Experts, This is first time we have implemented RPA to mimic a process which uses an application running in external Citrix client. We used surface automation (Region Spy Mode) for the interaction with this application. RPA development is complete for the entire application process and we are currently in our testing phase. Our RPA process seamlessly runs in our runtime resource virtual machine(VM in DEV environment) when the VM window is OPEN. The moment we close this runtime VM window at any point in time while the RPA is running for this process, it fails.  Is there any limitation with surface automation to keep runtime resource VM window OPEN?  Any guidance would be appreciated as this is urgent for us to resolve.  Thanks, Shweta Pandey   Fri, 11 May 2018 20:44:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86284#M37158 ShwetaPandey 2018-05-11T20:44:00Z https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86285#M37159 Hi Shweta, Even I'm facing same issue. When I run it in attended mode it runs without any issue but when I run in unattended mode, it gives different output. I'm working on Citrix application. How do you resolve this issue? Can you please help me?  Thanks & regards, Rohini Sun, 13 May 2018 21:16:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86285#M37159 RohiniPatil1 2018-05-13T21:16:00Z https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86286#M37160 Are you accessing the resource machine via RDP (mstsc)? RDP is not a suitable access tool and is specifically not recommended by BP. The reason RDP doesn't work with surface automation is that the remote desktop only exists when you have the window open, and is destroyed once the window is closed. After closing the window BP is still running on the remote machine, but there is no UI, so any process that requires the UI (global click, keystroke, screenshot, SA) will encounter problems. You can test this by running a process that captures a screenshot - when the window is closed the screenshot will be black. One solution is to use a remote access tool where the target machine persists, and is unaffected by you viewing it (see link above). Another solution is to use Login Agent to log in and to run the process unattended. And if you do connect via RDP, you must run the Log Out and Log In processes to reinstate the remote desktop. Mon, 14 May 2018 13:11:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86286#M37160 John__Carter 2018-05-14T13:11:00Z https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86287#M37161 Thank you John for the response! We are not using RDP. Instead, using Radmin to access our virtual machines. With Radmin, our target runtime virtual machines persists. UI interactions such as global clicks, keystroke, etc works as expected if not used for 'Region Spy Mode' elements. It is currently failing only for surface automations and only when the runtime resource (unattended) window is closed. Process works fine when the window is open and/or minimized. I am wondering if there are any limitations with Radmin for surface automation. Wed, 16 May 2018 23:15:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86287#M37161 ShwetaPandey 2018-05-16T23:15:00Z https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86288#M37162 Are you using images to check the window exists or not? If yes, and if you want to use the same code in Unattended mode, it won't work. You have to take screenshots in unattended mode and then use that pictures for ""Image Search - Business object"". The resolution of the VM in unattended mode is fixed, so images and their grey scales change accordingly, that why it doesn't get the same grey scale or color scale as in the attended mode, (when VM is ""open).  Thanks, Arshu Wed, 24 Oct 2018 13:09:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-automation-using-Region-Spy-Mode-fails-when-runtime/m-p/86288#M37162 ArshuHansda 2018-10-24T13:09:00Z