cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
HEATFreight
Kudo Kingpin
Kudo Kingpin

Power Automate Desktop Fails in New Microsoft Edge Build Version 90.0.818.56 Due to Edge Window Title Changing Depending on Which Tabs Are Open

Power Automate Desktop Fails in New Microsoft Edge Build Version 90.0.818.56 Due to Edge Window Title Changing Depending on Which Tabs Are Open

ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL. 


I have the latest versions of Power Automate Desktop (2.8.73.21119) and Microsoft Edge (Version 90.0.818.56).

With previous builds, I never had a problem getting my flow to open a particular webpage in Edge and keep it refreshed.

That's all I need this flow to do: KEEP ME LOGGED INTO THIS WEBSITE. But the logic for that is more complex than you might think at first glance. The reason is because there are multiple states for which this flow may run:

*Already logged in with an active website session for the target URL and Edge Window is open (either minimized, restored, or maximized)

*Already logged in with an active website session for the target URL but Edge process not running (if for instance Edge has not been launched since last reboot of the Hyper-V VM in which I'm running PAD) -
In this case, launching Edge and navigating to the target URL should take me to an active session without needing to login again

*Not logged in, but target URL was the last website open -
In this case, launching Edge should take me to the login page for the target URL

*Whether logged in or not, the target URL is not the current webpage. i.e. some other Edge windows are open or the current Edge window has some other tab open instead of the target URL. This could be a blank new tab or it could be some other webpage.


So here is my problem: depending on which state the VM is in when the flow is launched, the Window Title of the open Edge browser will change. If Edge has already been launched since last reboot, my flow conditionals are able to differentiate between the login page for the target URL and the target URL itself (in an already logged-in session). Everything works as expected in this case. But the situation changes if the VM has been rebooted without launching Edge. Instead of a single Edge window with a single tab, we get whatever the last tab was + a new tab pointed at the target URL. THIS BREAKS THE FLOW, presumably because the Window Title changes depending on what tabs are open, even if the target URL is the open tab.

There's a relevant setting with three options that also contributes to the precise state of the Edge browser as it relates to PAD launching Edge. That setting is called "On startup" and the choices are OPEN NEW TAB, CONTINUE WHERE YOU LEFT OFF, or OPEN A SPECIFIC PAGE OR PAGES.

None of the three options fixes the problem! The problem is that flow actions which need to recognize the title of the Edge window can't do so if more than one tab is open, but the same issue happens regardless of which of those three settings we use.

OPEN A NEW TAB will cause a blank tab to open in the same window as the target URL.

CONTINUE WHERE YOU LEFT OFF will cause two tabs of the target URL to open (or if another webpage was previously open instead of the target URL, then you get one tab with the previous page and one tab pointed at the target URL).

OPEN A SPECIFIC PAGE OR PAGES (with the target URL as the sole webpage) will also result in two tabs -either one blank tab and one tab pointed at target URL or two tabs pointed at target URL, depending on the previous state of Edge.

As I said, if Edge has already launched since last reboot, the flow works fine (assuming the target URL or its login page is the only open Edge tab/window).

The flow fails if some other website is open in an Edge tab/window or if Edge has not been launched since last reboot. I can cause the flow to succeed if I open and close Edge after reboot. But depending on which "On startup" setting is selected, the flow may fail if the last open webpage was something besides the target URL or its login page. If Edge has been opened with a blank tab since last reboot, then I'm pretty sure my flow logic works. But if Edge has been opened with some website other than the target URL, whether that Edge window is still open or not, it seems that launching Edge pointed at the target URL will always result in two tabs: either one blank tab and one target URL tab or one tab with previous webpage and one tab with target URL.

ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL. 

How can I force Edge to always open just the webpage I want?

Remember, CONTINUE WHERE YOU LEFT OFF and OPEN A SPECIFIC PAGE OR PAGES do not work 100% of the time. They fail if Edge has not been launched since last reboot. In this case, WE ALWAYS GET TWO TABS.

The only way I can get it to just open the one tab is if Edge has already been launched and if the only open tab is either the target URL or its login page. In this case, the flow logic works flawlessly.

Previously, with other builds, we never had any trouble getting Edge to open just the one tab with our target URL.

Come on Microsoft, what gives? Why you gotta keep changing crap on us? My flows had to all be re-tagged because you guys got rid of the default Windows-style download dialogues and replaced them with a cleaner downloads button and dialogue built directly into Edge. Well that's great and all but you screwed us over by doing so!

But I fixed that, no big deal. Now it's the [one tab] vs. [multiple tabs] window title discrepancy that's killing us!

I don't suppose there will be a literal fix for the problem so much as a workaround. Can anyone help me think of some logic that would solve this problem? I have tried PowerShell scripts to look for and close all open Edge windows/tabs, but it's hard to make this work even when some Edge windows could be  minimized. And forcing Edge windows to close results in errors from Edge trying to CONTINUE WHERE YOU LEFT OFF or whatever it does. It's completely unclear to me how to get the "On startup" setting to work flawlessly with PAD. 

Oh and to further complicate matters, keep in mind that launching a PAD flow from the cloud vs. launching a PAD flow from the PAD editor vs. launching a PAD flow from the PAD console do not give you the same results! There are certain classes of errors that only happen if you launch from the cloud or maybe the console, but which will not happen when launched from the editor! WTF Microsoft!


ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.
ALL I WANT IS EDGE TO NEVER OPEN ANOTHER TAB BESIDES THE TARGET URL.

1 ACCEPTED SOLUTION

Accepted Solutions
HEATFreight
Kudo Kingpin
Kudo Kingpin

I think I have it in a stable configuration with the following steps:

(1) >On startup >Continue where you left off [target URL] +

(2) Edge shortcut saved in my startup folder +

(3) this PowerShell command executed within my PAD flow right before the "Launch New Edge and navigate to target URL" action:

 

taskkill /im msedge.exe;

 

 
But this only works assuming no other Edge windows or tabs are left open besides the target URL. If it's in that configuration, then even though upon reboot Edge opens up with two tabs, my logic will kill the active two-tab Edge window GRACEFULLY and then relaunch Edge to just the one target URL. 👍👍

Quite an elaborate bit of logic to reliably achieve such a simple task of refreshing/logging into a website with only a single tab open. Here's some pseudocode:

 

if(Tab Example.com is open){
Launch New Edge and attach to tab Example.com and store instance into Browser;
Set Window State tab Example.com Maximized;
Send Keys {LControlKey}({R}) to the active window;
Stop Flow successfully;
}

if(Tab Login-Example.com is open){
Launch New Edge and attach to tab Login-Example.com and store instance into Browser;
Set Window State tab Example.com Maximized;
Click UI element in window Button 'LOGIN';
Stop Flow successfully;
}

if(Tab Example.com is not open){
Run PowerShell script taskkill /im msedge.exe;
Launch New Edge and navigate to tab Example.com and store instance into Browser;
Click UI element in window Button 'LOGIN';
Set Window State tab Example.com Maximized; //not sure why i maximize this one after clicking, but it's working so i hesitate to change anything ¯\_(ツ)_/¯
Stop Flow successfully;
}

 

 

View solution in original post

2 REPLIES 2
HEATFreight
Kudo Kingpin
Kudo Kingpin

I have discovered that I can prevent Edge from opening with two tabs if I close it and re-open it.

I don't know how to make Edge open just the one desired tab on launch, but I added it to my startup folder anyway. So now if my "refresh" flow runs after the VM has rebooted, the Edge process is already running and this means I can close and relaunch it with just one tab.

What a frickin sh t show! Should not be this difficult to reliably open a single tab!

HEATFreight
Kudo Kingpin
Kudo Kingpin

I think I have it in a stable configuration with the following steps:

(1) >On startup >Continue where you left off [target URL] +

(2) Edge shortcut saved in my startup folder +

(3) this PowerShell command executed within my PAD flow right before the "Launch New Edge and navigate to target URL" action:

 

taskkill /im msedge.exe;

 

 
But this only works assuming no other Edge windows or tabs are left open besides the target URL. If it's in that configuration, then even though upon reboot Edge opens up with two tabs, my logic will kill the active two-tab Edge window GRACEFULLY and then relaunch Edge to just the one target URL. 👍👍

Quite an elaborate bit of logic to reliably achieve such a simple task of refreshing/logging into a website with only a single tab open. Here's some pseudocode:

 

if(Tab Example.com is open){
Launch New Edge and attach to tab Example.com and store instance into Browser;
Set Window State tab Example.com Maximized;
Send Keys {LControlKey}({R}) to the active window;
Stop Flow successfully;
}

if(Tab Login-Example.com is open){
Launch New Edge and attach to tab Login-Example.com and store instance into Browser;
Set Window State tab Example.com Maximized;
Click UI element in window Button 'LOGIN';
Stop Flow successfully;
}

if(Tab Example.com is not open){
Run PowerShell script taskkill /im msedge.exe;
Launch New Edge and navigate to tab Example.com and store instance into Browser;
Click UI element in window Button 'LOGIN';
Set Window State tab Example.com Maximized; //not sure why i maximize this one after clicking, but it's working so i hesitate to change anything ¯\_(ツ)_/¯
Stop Flow successfully;
}

 

 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,033)