@MayAnnTenorio The Universal Web Adapter (UWA) is fundamentally different than the IE adapter. The UWA attaches to Chrome or Edge not by the process launched by Runtime, but instead by the extension launching a process named "OpenSpan.Translators.Web.MessagingHost.exe". This means that once your adapter has started and has registered with the MessagingHost process, that any pages in any instance of that browser can be recognized by the adapter. This means that if you were to open multiple instances of the same application, the adapter will match pages in both windows because the actual process is not tied to the adapter: only the pages are.

The easiest way you can segregate these is to use different browsers. For your automations, use Chrome and have the users launch their own copies in Edge (or vice versa). The adapters are tied to a specific browser, so there would be no matching of pages within the Edge windows. If you can only use one browser, then you'll likely need to take a more complex route. You can enable UseKeys on each page and then track the BrowserForm.WindowHandle property of each page to determine if it is within the window you wish to automate. Each UWA page has a property named BrowserForm that is a reference to the Window that the page is within. This form has a Window Handle which you could use to differentiate between windows within your automations. The only challenge here is when you have an application that spawns multiple windows (or if you have users who wish to use the same window for two copies of an application in separate tabs). The latter would not work, however the former is possible by observing the window that launches the new window and then associating that handle with your initial one.

We may have functionality added in the future to address this by using alternate browser profiles, however we currently have no ETA on when this might be available as it is still being discussed.