https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62885#M15919 This is an error I have ran into from time to time as well, with different root causes. My first suggestion is to double check that when you are modeling the application you are interacting with that Match Index is always used as an identifying criteria. This ensures that BP is looking for the correct window. Not 100% guaranteed as a fix every time, there may be something else at work, but a good place to start. Tue, 13 Mar 2018 19:43:00 GMT Robert_WilliamL 2018-03-13T19:43:00Z https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62884#M15918 Hello BP Advocates, I've stumbled upon an issue regarding an internal error that I have no knowledge in handling, the full error message: We can launch the application and maximize - it's when we use the "Activate Application" is when we get this error ERROR: Internal : Failed to perform step 1 in Navigate Stage "Activate main window" on page "Navigate" - Could not identify process owning the current foreground window. Is there any possible fix/workaround to this issue Regards, R   Tue, 13 Mar 2018 19:11:00 GMT https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62884#M15918 Ricky__Sangalli__Korletey 2018-03-13T19:11:00Z https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62885#M15919 This is an error I have ran into from time to time as well, with different root causes. My first suggestion is to double check that when you are modeling the application you are interacting with that Match Index is always used as an identifying criteria. This ensures that BP is looking for the correct window. Not 100% guaranteed as a fix every time, there may be something else at work, but a good place to start. Tue, 13 Mar 2018 19:43:00 GMT https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62885#M15919 Robert_WilliamL 2018-03-13T19:43:00Z https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62886#M15920 I've encountered this error in my current process. It happens when you have 2 of the same process running, and you are trying to use AA element actions. Detaching/Attaching seems to have dampen the occurrence rate. Wed, 14 Mar 2018 19:14:00 GMT https://community.blueprism.com/t5/Product-Forum/Internal-Error-Could-not-identify-process-owning-the-current/m-p/62886#M15920 MartinWu 2018-03-14T19:14:00Z