cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

"Populate text Field on web page" action failed by error message "'appmask' isn't an appmask"

If I run a desktop flow from PAD Console window, an error occurred at "Populate text Field on web page" action.

But if I debug run (F5) the same flow from PAD Flow Designer window, it runs successfully without any problems.

 

I have found that there is "Actions.log" file under below folder path, and it says "PopulateTextFieldBase" action failed by error message "'appmask' isn't an appmask"
C:\Users\{UserName}\AppData\Local\Microsoft\Power Automate Desktop\Console\Scripts\{GUID}\Runs\{GUID}

 

I have one input variable which has "Sensitive Text" type.

And if I changed the type of this input variable to plain "Text", above error is disappeared and flow completed successfully.

 

Also, I found that above error occurs in newer PAD version 2.12.171.21216, but not in older PAD version 2.10.36.21161.

Tried with two different PCs with PAD version 2.12.171.21216, and they have same issue.

 

 

IMPORT 'C:\\Users\\{UserName}\\AppData\\Local\\Microsoft\\Power Automate Desktop\\Console\\Workspace\\{GUID}\\A85791E3\\controlRepo.appmask' AS appmask
IMPORT 'C:\\Users\\{UserName}\\AppData\\Local\\Microsoft\\Power Automate Desktop\\Console\\Workspace\\{GUID}\\A85791E3\\imageRepo.imgrepo' AS imgrepo
@INPUT KEYWORD : { 'Description': 'Input search keyword.', 'FriendlyName': 'KEYWORD', 'DefaultValue': P'', 'Type': 'Sensitive' } 
WebAutomation.LaunchEdge Url: $'''https://www.bing.com/''' WindowState: WebAutomation.BrowserWindowState.Normal ClearCache: False ClearCookies: True Timeout: 60 BrowserInstance=> Browser
WebAutomation.FormFilling.PopulateTextField BrowserInstance: Browser Control: appmask['Web Page \'https://www.bing.com/\'']['<input:search> \'sb_form_q\''] Text: KEYWORD EmulateTyping: True UnfocusAfterPopulate: False Mode: WebAutomation.PopulateTextMode.Replace

 

 

shindomo_0-1629608676045.png

 

Is there any known issues or bugs related to above error in PAD version 2.12.171.21216?

Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions
PetrosF-MSFT
Employee
Employee

Hi @Anonymous and @HEATFreight thank you for bringing this issue to our attention. It has been acknowledged and will be resolved in the September update.

In the meantime, please note that the Desktop flow runs successfully when it is executed from the PAD Designer or triggered through a Cloud flow.

View solution in original post

8 REPLIES 8
HEATFreight
Kudo Kingpin
Kudo Kingpin

I'm getting the following error from "Populate text field on web page":

 

'appmask' isn't an appmask 

 

 

 


This only occurs when I run the flow from outside the editor, like from the PAD console or from a cloud trigger. If I run from the editor, everything works fine 🤷‍

By the way, we have the same PAD version as @Anonymous 

 

PAD version 2.12.171.21216

 


This is not the first time we have seen actions that worked in the editor but failed when running flow from console or cloud. Previously we were able to find robust workarounds, but we had a long screenshare with a Microsoft tech support rep, and even they were not able to find a good workaround in this case.

Well he did make a workaround that tries to click into the login credential fields which are giving us trouble, but he used a "Move mouse to image" action, which is not as robust as a "Populate text field on web page" action. However, even the "Move mouse to image" action fails, but only when running outside of the PAD editor! Works fine in editor. Fails from console or cloud! This action gives the following error:

 

'imgrepo' isn't an appmask 

 



Also, we use the latest version of Microsoft Edge browser. The Microsoft rep said to try the flow in Chrome as well, and we will even try it in IE or the automation browser too if Chrome doesn't work.

It could be that this website is goofy, but then why does the flow run perfectly in the editor? Why would it only fail when running from console or cloud? Certain goofy websites are causing a corner case where flow actions only work in the editor. This could possibly be fixed by the developers of the affected goofy websites, but it seems obvious to me that PAD devs could also fix this corner case.

It's worth noting that we are quite experienced at editing element selectors to be simpler and more robust. We have tried both Web-type automations as well as UI-type (window) automations, and we are able to make either type work, but only when running from the editor. For this particular website, neither Web or UI automations work from console!

Please investigate this issue, Microsoft! It's probably less of a corner case than it seems. I would bet that this same issue is causing all kinds of problems, which people are simply finding workarounds for. It's rare for all workarounds to fail in the same way, but this is definitely not the first time we have come across actions which only work in the editor but never in the console. It's just the first time that every workaround we have tried was also subject to the same failure mode.

Thanks for reading!

PetrosF-MSFT
Employee
Employee

Hi @Anonymous and @HEATFreight thank you for bringing this issue to our attention. It has been acknowledged and will be resolved in the September update.

In the meantime, please note that the Desktop flow runs successfully when it is executed from the PAD Designer or triggered through a Cloud flow.

@PetrosF-MSFT Wait are you telling me that if we trigger the affected Desktop flows from the cloud they will work?

It has been my experience that when something works when running in the PAD Designer but not in the PAD Console, it will also have the same error when running from the Cloud as it does from the Console.

Technically I have not tried running this particular flow from the Cloud due to what I learned from my past negative experiences. After so many frustrating experiences, I have always tried to find a workaround that runs successfully from the Console before I deploy in a Cloud flow. Guess I'll get this built into a Cloud flow proof of concept to test that functionality. Would be really amazing if it just works!

Also, we have a seemingly separate issue in the affected flow. Don't think it's related but...

Oddly enough with this particular website that we're trying to automate, there is another issue with "Populate text field on web page" which is that the fields appear to be filled, but upon clicking LOGIN button, the fields get wiped and login fails. If for instance I but a debug point right after filling the password field, then I can click out of the filled password field and it will wipe itself. If I click the button to reveal the password, the password disappears. If we have the automation click the reveal password button before inputting the password, then pause the flow, yet again clicking out of the password field wipes it, or clicking the hide password button will also clear it out. Something similar is happening with the username/email field, although it does not wipe itself. The website is rejecting the input for both login credential fields, but only when using the Web Page action. When using the Window (UI) action, it works fine every time! (unless we run from console...). To be clear, the Web Page action does appear to fill the fields with the input (text boxes turn yellow and the text appears within), it's just that the input gets wiped upon submit. 

Here is the workaround we devised for this issue: after filling each field with the "Populate text field on web page" action, we click into the text field and backspace the last character, then send that key again. Somehow this causes the website to accept the input. LOGIN button works fine after this little workaround. But if we are going to this extreme, why even use the "Populate text field on web page" action in the first place? Why not use only Mouse and Keyboard actions if these are required to make this field work? Well because either workaround compromises robust functionality. We hate using Mouse and Keyboard actions because they are not as robust as sending inputs directly to a particular element within a web page or window. It's unclear to us why —only on this one particular website— the "Populate text field on web page" action is not accepted. This error happens no matter where we run the flow (Designer or Console, actually haven't tried Cloud yet).

I should probably make a new thread about this as I don't think it's at all related to the other issue...

Anonymous
Not applicable

I'm having a similar issue  and I'm using the latest version of PAD.  The error below is only being caused while running from the console or cloud not the designer. 

'appmask' isn't an appmask

 

Argument 'BrowserInstance' must be 'Web browser instance'. 

Anonymous
Not applicable

Hello @HEATFreight @PetrosF-MSFT @Anonymous 

 

I confirmed this issue is fixed in PAD Version 2.13.138.21255.

 

I appreciate Microsoft's effort to resolve our problem.

GhitaFjorback1
Helper II
Helper II

@PetrosF-MSFT  Hi, I am glad the above is fixed, but I am now having the same issue, only the other way around. 

When I populate text in webpage, no sensitive text, it will run smoothly as long as my Desktop flow is either in debug run mode, or run directly from the designer. If I trigger the Desktop flow via Power Automate Flow, the populate text action will simply not work (attended run)! This is getting frustrating. Does anyone have a solution for this issue? I am running the latest version of Desktop Flow 2.13.138.21255

 

Thanks

@GhitaFjorback1 have you tried "Populate text field in window"?

My understanding is that web-type actions —when they work— are always preferable to UI-type (window) actions, but web-type doesn't always work. Obviously editing the element selectors can help, but it sounds like that's not your problem here because when the element selector is at fault, well I don't think the action works at all in that case. And you say it works fine in designer, so must not be element selector causing the issue.

In my flows, I use web actions and UI actions interchangeably depending on what seems to be working and what seems to be hanging up. I have had trouble with fields on certain websites when using "Populate text field on web page", where basically the field turns yellow and appears to populate correctly, but the input is not accepted. When logging into one particular website for example, the username and password fields visually appear to populate just fine, but the inputs are cleared out upon clicking "LOGIN" (actually I send ENTER key instead of "Press button on web page" / "Click UI element in window" / "Press button in window" because the "LOGIN" button on this particular website was also giving me trouble with all three of those click actions).

If I click the "unhide password" button, my password input disappears. If I have automation click that button before password input, I can see the password populates correctly, but if I then have the flow pause and I click anywhere at all, the password is cleared out. The same thing is happening with the username field except that it never disappears, but the input is not accepted regardless.

Two workarounds I have found in these situations are:

a) After "Populate text field on web page" I "Send a mouse click" to the coordinates of the field and then "Send keys" and type one extra character, then backspace that character. This causes the input to be recognized, but it's a sloppy workaround because you never want to use on-screen coordinates if you can avoid it. I call these "naked mouse clicks" because they are not tied to the web/UI element that they are meant to interact with, hence they are riskier. And if you are using naked clicks, you might as well skip the "Populate text field on web page" and just use all "Mouse and keyboard" actions to click and send keys.

b) Just use "Populate text field in window" instead. Like I said, you would rather use "Populate text field on web page" if you can get it to work, but to the extent that the web element in question has a UI-type counterpart, you should be able to get "Populate text field in window" to work even when the web-type action would otherwise fail, although it may take some experimentation with the element selectors to get it functioning reliably. Also, I only ever have one Edge window open and one tab in that window. I have found the UI-type element selectors to be unreliable when multiple Edge windows are open or when one Edge window has multiple tabs. These situations subtly change the window elements such that element selectors fail, and I have not figured out how to deal with that. So always use a single tab in a single window if you can. To be sure that the automation never opens an Edge window with an existing tab besides my intended one, before I "Launch new Edge" I use "Run PowerShell script" with

 

taskkill /im msedge.exe /F;

 

I'm not sure if the PowerShell script is still necessary, because different versions of Edge may or may not have the unwanted tab issue, which is also affected by the "When Edge starts" setting. I use "Open new tab page" for that setting. Another thing I've noticed is that, in terms of the unwanted tab problem, Edge may behave differently upon first launch after reboot as compared to subsequent launches. The PowerShell script puts Edge into the same state at every launch, so behavior is more predictable. And when my flow is done I run that same PowerShell script again to hopefully prep for the next flow run. I'm not sure that force-quitting Edge is the best solution for this, but it has ensured that my flows reliably open only the one desired tab in Edge, which ensures that UI-type actions are able to find the correct window and its elements.

Anyway, so if your "Populate text field on web page" actions are seemingly working up until the moment that you "submit" your inputs to the web page, at which point the inputs disappear or are otherwise not accepted, then you probably have the same problem I was having, and you would probably benefit from using UI-type "Populate text field in window".

Or if your "Populate text field on web page" actions are not turning the text fields yellow at all and you are not seeing any inputs populate those fields, then you are having a different issue, but you may still benefit from experimenting with UI-type "Populate text field in window".

Apologies for long-winded response, but hopefully it helps someone!

@HEATFreight  Thank you so much for your fast and thorough reply!
It actually helped by changing to Populate "UI" instead of "Web" action! Thank you.

I still need to tell Microsoft though that although we can find a workaround, it is really not good that designer and flow trigger is not behaving alike! We test and test, and when we go live, we expect the desktop flow to behave the same no matter how it is triggered. 😞

 

Thanks again! Highly appreciated!

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders   UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

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.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (2,751)