Subject: Issue with Microsoft Edge Download Dialog - Selector Not Working When Run via Orchestrator

Help Activities
, , ,
1

Hello everyone,

In one of our automation processes, the bot downloads two files from a website using a web browser.
Previously, this worked reliably with Mozilla Firefox—both when running the process locally (on my development laptop) and when executed through Orchestrator on the bot machine.

Recently, we switched to Microsoft Edge as the browser. Since then, the download process no longer works correctly when the process is run via Orchestrator on the bot machine.

Here’s the key point:

When I test the process locally on my development laptop, it works fine.

Even when I remotely debug the process on the bot machine, the download also completes without issues.

However, when the process is executed via Orchestrator, the bot fails to interact with the “Save As” button in the Edge download dialog. The selector does not seem to be recognized, and the file is not saved.

I will explain what the Bot is supposed to do:
After clicking the download button on the website, the Microsoft Edge download dialog appears.

image
image463×218 8.47 KB

The bot should then click on the “Save As” button (“Speichern unter”), enter the desired file path, and confirm the save.

Unfortunately, the selector for the “Save As” button is not working during unattended execution via Orchestrator.

Here is an example screenshot of the selector I am using:

image
image936×706 68.3 KB

What I’ve tried so far:

  1. Using different UI frameworks (Default, Active Accessibility, UI Automation) to build the selector.

  2. Sending keyboard shortcuts: for example, clicking into the dialog window and navigating to “Save As” using Tab and Enter via “Send Hotkey”.

All these approaches work when I run the process locally and even during remote debugging on the bot machine.

But again, none of these work when the process is triggered via Orchestrator.

Both the development environment and the bot machine are using Microsoft Edge version 135.0.3179.54.
I am using “UiPath Studio 2023.10.10”.
The Orchestrator runs on “Orchestrator 2023.10.8”.

Has anyone experienced similar issues or can suggest a reliable way to interact with the Microsoft Edge download dialog during unattended execution?

I would be very grateful for any suggestions or help!

Kind regards
FlorianP

2

@FlorianP

first try hardware events

second use a separate use application browser

third we can avoid this by changing the setting in edge to auto download to downloads folder and then we can use move file to move to any location that you need..this would avoid the clicks all together

cheers

3

Hey @FlorianP are you working on Community version if yes then many of the fellow member are facing that type of problem.as per the solution is go to orchestrator remove the machine and add that same machine again that it will generate client ID and client Secret copy that and paste it to the assistant where are you running your unattended bot. now your are good to go to run your process again. and before doing that if this happen in type into or any ui activity kindly enable the simulate/send window from the property panel of that activity.

cheers

4

This is a common issue when automations behave differently between attended and unattended (Orchestrator) runs—especially with system dialogs like the Edge download prompt.

Here are a few suggestions that might help:

  1. Use “Send Hotkey” Activities: Since the Edge download dialog is part of the browser’s native UI, selectors may not always be reliable. Try using Send Hotkey (e.g., Ctrl + J to open the Downloads page or Tab + Enter to navigate and confirm the download).
  2. Simulate UI with Image or Keyboard-Based Automation: Consider using image-based automation (like Click Image) or Type Into with simulated keys. This bypasses selector issues altogether.
  3. Check Orchestrator Robot Settings: Ensure the robot runs in interactive mode with a properly loaded user session (resolution and login settings). Sometimes selectors fail if the screen isn’t fully loaded or visible during execution.
  4. Add a Delay or Retry Scope: The dialog might not appear instantly. Wrap your action in a Retry Scope with a small delay to wait for the download dialog to become available.
  5. Switch to Modern Design Experience: If you’re still using classic activities, switching to the modern experience can offer more resilient UI interaction methods.

If possible, share the selector or a screenshot for more targeted help.

Hope this helps!

5

Hi everyone,

Thank you all for your responses. While reviewing your suggested solutions, I noticed something in the error message (that i haven’t noticed before).
It turns out that when building the selector, UiPath consistently sets the class to cls='Chrome_WidgetWin_2' and while its running locally or through remote debugging, it also identifies the button with that class.

However, for some reason, when the process is executed via Orchestrator, it identifies the class as cls='Chrome_RenderWidgetHostHWND'.

By using a wildcard for the class value in the selector, I was able to make the process run successfully, even when triggered from Orchestrator.

Kind regards
FlorianP

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.