web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Different element type...
Power Automate
Suggested Answer

Different element types detected (“Pane” vs. “Window”) on the same machine with two user accounts

(2) ShareShare
ReportReport
Posted on by 123

Hello everyone,

I’m encountering an odd issue with Power Automate Desktop on the same machine but using two different user accounts (which I’ll refer to as Robot 4 and Robot 1). When I log in as Robot 4, the target element (e.g., “Save As” window) is detected as a “Pane”, which is what I need. However, when I log in as Robot 1 on the very same computer, the exact same element is recognized as a “Window”.

I’ll attach two screenshots illustrating this difference:

  1. Robot 4 → Element detected as “Pane”
  2. Robot 1 → Element detected as “Window”

Because I want to run the same flow for both users on the same machine, the discrepancy causes issues—one user always ends up failing to interact with the element.

Could anyone help me understand why Power Automate Desktop is labeling the same UI element differently between these two accounts? And most importantly, how can I force or maintain the element detection as “Pane” for both users so the flow runs consistently?

Thanks in advance for any insights or suggestions!

I have the same question (0)
  • Suggested answer
    Gonzalo Brückmann Profile Picture
    3 on at
    I had the same issue, but with same user account on different machines.

    You have two ways, one is to check for both, if window fails check for pane.

    The other way you can fix this is by removing completely that word by toggling "Text editor" and editing it manually
     
    For example, my Preview text selectors on the main window are this two:
    :desktop > pane[Class="Chrome_WidgetWin_1"][Process="chrome"]
    :desktop > window[Class="Chrome_WidgetWin_1"][Process="chrome"]
     
    you can actually remove it and leave it like this:
    :desktop > [Class="Chrome_WidgetWin_1"][Process="chrome"]
     
    in my case this solved the issue hope it helps
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 519 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 296 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard