I haven't personally had a case like this. Your error is not very descriptive, as it simply says it failed, but does not actually contain any details. Would be great if you could add a Get last error action on error and log the message somewhere. Or at the very least, look at the Windows Event Viewer and see if there are any errors in the Application logs that would correspond to the flow failing.
What I would suggest is to avoid using the Launch new Chrome (or any browser) action for actually launching the browser. The action depends heavily on the extension loading in time. It is quite frequent that the browser window is launched, but the extension lags behind and thus PAD assumes the action failed. This is a frequent issue.
I would thus suggest using the Run application action to launch the browser and then use the Launch new Chrome action to attach to it. This is a much more stable approach and I've been using it for years.
Here's what it would normally look like:
This flow uses the Run application action to launch the Chrome app, passing in a default web page (in this case Google) as the parameter, waits for the window to appear (using Google as part of the window name, so it also waits for the page to load) and then attaches to it. This works all the time without the inconsistencies of the Launch new Chrome action.
You can also copy and paste the following code into your PAD designer to get the same set of actions:
SET URL TO $'''{SomeURL}'''
System.RunApplication.RunApplication ApplicationPath: $'''chrome''' CommandLineArguments: $'''www.google.com''' WorkingDirectory: '' WindowStyle: System.ProcessWindowStyle.Maximized ProcessId=> AppProcessId
WAIT (UIAutomation.WaitForWindow.ToOpenByTitleClass Title: $'''Google*''' Class: $'''Chrome_WidgetWin_1''' FocusWindow: True) FOR 30
WebAutomation.LaunchChrome.AttachToChromeByTitle TabTitle: $'''Google''' AttachTimeout: 5 BrowserInstance=> BrowserMain
ON ERROR REPEAT 5 TIMES WAIT 3
END
WebAutomation.GoToWebPage.GoToWebPageCloseDialog BrowserInstance: BrowserMain Url: URL
Note that {SomeURL} in the snippet should be replaced with the actual URL to navigate to.
It can easily be modified to use a different browser, too, by adjusting the application to be launch and the browser to be attached to.
-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution.
If you like my response, please give it a Thumbs Up.
If you are interested in Power Automate, you might want to follow me on LinkedIn at https://www.linkedin.com/in/agnius-bartninkas/
