Context: I am building an automation for a web-based system (“ISIS Cloud”). The process involves logging in, which triggers the application to open a new browser tab to display the main dashboard.
The Problem: The Use Application/Browser activity I am currently using is scoped to the initial login page. Once the login process finishes and the new tab opens, the automation is unable to interact with the elements in the new tab.
I have tried wrapping the next steps in a separate Use Application/Browser activity, but it fails to recognize the new tab or keeps prompting for a “File path” (even though I only need to attach to the existing session).
What I’ve tried:
I have verified that the UiPath extension for Chrome is active.
I attempted to use a secondary Use Application/Browser activity for the dashboard tab, but it doesn’t seem to correctly “attach” to the existing Chrome process.
Questions:
- What is the best practice to handle scenarios where an application opens a new tab after login?
- How can I properly “attach” to the new tab so the robot can continue the process without trying to re-open the browser or throwing a “File path is required” warning?
Any advice on how to correctly configure the selectors or the activity settings to maintain the connection across tabs would be greatly appreciated.

