https://community.blueprism.com/t5/Product-Forum/ForeGround-Issue/m-p/50037#M5334 Setforeground window errors usually occur where the desktop does not exist - so the screen is locked or you are connecting to the resourcepc via RDP and disconnect. For global interactions (Activates, Global Clicks, Global sendkeys) to work the desktop needs to exist and not be locked. The VM technology that is used needs to provide persistance and consistancy (unlike RDP connections) - Please refer to the product documentation and reference guides. Tue, 28 Feb 2017 13:46:00 GMT John__Carter 2017-02-28T13:46:00Z https://community.blueprism.com/t5/Product-Forum/ForeGround-Issue/m-p/50036#M5333 Hi Team, I am running a process from one robot to another. Process is ruining fine when we are running in same robot but it is not running while we try to run in another robot it giving a foreground element issue and global send keys are not working in robots. Please advise us. Thank you for your support Tue, 28 Feb 2017 11:26:00 GMT https://community.blueprism.com/t5/Product-Forum/ForeGround-Issue/m-p/50036#M5333 Anonymous 2017-02-28T11:26:00Z https://community.blueprism.com/t5/Product-Forum/ForeGround-Issue/m-p/50037#M5334 Setforeground window errors usually occur where the desktop does not exist - so the screen is locked or you are connecting to the resourcepc via RDP and disconnect. For global interactions (Activates, Global Clicks, Global sendkeys) to work the desktop needs to exist and not be locked. The VM technology that is used needs to provide persistance and consistancy (unlike RDP connections) - Please refer to the product documentation and reference guides. Tue, 28 Feb 2017 13:46:00 GMT https://community.blueprism.com/t5/Product-Forum/ForeGround-Issue/m-p/50037#M5334 John__Carter 2017-02-28T13:46:00Z