Multiple Edge Browser Issue
Hi,
We're encountering a intermittent issue with one of our automations.
it gets stuck upon launching the 2nd edge adapter. base on the logs its saying that It can't find the window but it just waiting on the screen.
Is there an issue if we have multiple edge browser injected? how can this be fixed?
Thanks
Pegasystems Inc.
US
@angealll You should not have any issues with multiple Edge adapters. I don't believe that line specifically indicates a problem, however there may be something else going on. Are these adapters both using MonitorAll as the StartMethod?
Accenture
PH
@ThomasSasnett nope.all 3 edge adapter have BrowserStartMethod as Start.
But heres the setup.
Adapter 1 - 3 tabs, from login to actual details screen, left opened as bot need to update once done
Adapter 2 - 1 tab, left open as well, as bot would still use this for next screen
Adapter 3 - 2 tab, Landing page and Web app screen, bot closes once done with the process.
problem is that its just stuck upon starting Adapter 3, though im not really sure what happens.
but on the logs, its saying that adapter 3 can't see the window title for Adapter 2. which is odd
Pegasystems Inc.
US
@angealll I can't really see enough of your log to understand what is happening, but often times there are lots of messages about the windows and controls that are created that are not able to be associated with an adapter or a control. These are to be expected. During matching for example; you'll see lots of messages like "match rule failed for control...". This is an expected process as Runtime is attempting to look at each control and associate it with a specific control on the page itself.
Are you perhaps using the "AcceptedDomains" property of each adapter? That is designed to separate adapters so that you don't inadvertently match pages between different adapters. For example; assume that I have two adapters. One if for the Pega website and another is for the Accenture website. If I were to create a match rule for a page in the Pega adapter that was generic enough that it would potentially match a page within the Accenture website, then the matching would occur in the Pega adapter. Let's say for the login page I used a match rule that left the domain out of the URL and instead looked for the word "login" in the URL. This might also apply to a page within the Accenture website and thus could match within the Pega adapter. Do your automations work when testing them against one website at a time and only have issues when you run them together?
Accenture
PH
@ThomasSasnett AcceptedDomains property might work. we have not configured this yet in any of the adapters. During our dev testing, there were no issues whether we run it one at a time or all together during an end-to-end run. we just encountered this during our integration testing.
Pegasystems Inc.
US
@angealll Try setting that up. That will segregate your adapters. Basically Adapter A will only match pages with this string in the URL. Adapter B will only match these pages, etc...