Internal Error - Could not identify process owning the current foreground window
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-03-18 07:11 PM
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
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-03-18 07:43 PM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-03-18 07:14 PM
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.
