I'm using the Retrieve Email Messages flow action in my PAD flow and it continuous to throw this error, "Failed to retrieve message with uid 1853". This is a similar issue to the one described in this post: https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Retrieve-Email-Messages-returns-weird-err...
This is really frustrating. I'm not entirely sure why but this Flow is experiencing this issue in isolation. I have several carbon copies of this Flow with only minor changes to the actions, the most dramatic change being the "To" address the Retrieve Email Messages action looks for when performing - as well as changing the target folder path via a variable. Changing the folder path variable once changes the target folder throughout the flow.
Like I stated, I have other flows composed of the exact same actions with the primary difference being where the files are being placed and which email address is being used to filter the email messages with.
Here's the raw error information:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.: Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Failed to retrieve message with uid 1853. ---> System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.Format(String format, Object arg0)
at Microsoft.Flow.RPA.Desktop.Modules.Email.Actions.EmailActions.RetrieveEmails(Variant imapServer, Variant username, Variant varPassword, Variant mailFolder, Variant fromContains, Variant toContains, Variant subjectContains, Variant bodyContains, Variant sentSince, Variant sentUpTo, Variant saveAttachmentsInto, Variant& retrievedEmails, Int32 serverPort, Boolean enableSsl, Int32 retrieveOnlyUnread, Boolean saveAttachments, Boolean markAsRead, Boolean acceptUntrustedCertificates)
--- End of inner exception stack trace ---
at Microsoft.Flow.RPA.Desktop.Modules.Email.Actions.RetrieveEmails.Execute(ActionContext context)
at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)
I've tried the fixes @MichaelAnnis suggested in the attached post, but it's not making the Flow work anymore. I've also tried two full reboots, turn the computer all the way off, unplug, plug back in, turn on... nothing.
Some of my job is relying on this Flow's smooth operation. Arg.
Any suggestions as to what might be the cause?
****Edit:
I've built a much more condensed flow to test if PAD will throw the same or similar error for just the "To" string I supply.
It works, but now the Retrieve Email Messages behavior is way out of wack. I have it set to retrieve only read emails, and to only gather emails with a string in the "To" field. There's only 1 email that meets criteria of 9 total emails. Each run the Flow will wrongly grab EVERY email, not just the 1 qualifying email. If I change only the "To" field string, it behaves as normal and retrieves only the correct email. If I change the "To" string back to my desired target, it retrieves EVERY email.
In my primary flow, the one throwing the uid 1853 error, I can change the "To" field to anything other than my target string and it will work correctly.
Arg!
Solved! Go to Solution.
Troubleshooting guide:
If your Retrieve email messages Flow action is not retrieving anything at all and fails upon running there's something behind the scenes that's gone sour. PAD does not store all of its necessary tidbits on the machine running the PAD instance. PAD downloads the Flow from a server. If there's an issue with the stored PAD Flow you'll always pull out the same issue when running the Flow.
First try turning PAD on and off again.
Next try turning the machine on and off again, full reboot. Let it power down completely and then power back on after about 5 minutes of down-time.
If the issue persists, next try uninstalling/reinstalling PAD.
If the issue still persists, next try reviewing your Data Connections in your Office 365 account controls. Office Portal -> Power Automate -> Data -> Connections -> Create connection to Outlook
If the problem persists follow the below steps:
Create a new Flow from the PAD window. Name your Flow something useful. In your new Flow, create the following actions:
1. Launch Outlook
2. Retrieve email messages
3. Close Outlook
4. Display message w/ %RetrievedEmails% in the body text.
Set up your Retrieve email messages action to dispense every email in your inbox folder. In the Retrieve email messages action email filters options: "Mail folder:" should read "Inbox" (no quotes) for just inbox messages. If this does not work, you'll need to contact Microsoft support for more help. If this works, continue reading. Narrow your target down towards your goal. Mine is to get into a subfolder and retrieve particular emails based on some criteria. Next either target a subfolder "Inbox/yoursubfolder" or modify the "to contains", "from contains", etc, fields one at a time. Continue to run your Flow after each modification. If your Flow fails to retrieve anything with your particular needs, you will likely need to contact Microsoft support. If your Flow succeeds and your message box displays all of your desired information you've successfully overcome whatever hang-up was in your previous problem-Flow.
Once your new Flow is working as intended you can now open your problem-Flow and copy/paste the other Flow actions into/around the new Retrieve email messages Flow actions. Keep in mind however that changes to directory paths or file structure will need to be reflected in the Flow actions.
Hope this helps anyone. I've been battling this issue about 3 times now, each time it's a little more particular.
This part should be an easy fix, if you see what is causing this error:
"Index (zero based) must be greater than or equal to zero and less than the size of the argument list."
I have also seen "TO" field fail if you are trying to search for a distribution list. For instance:
Retrieve emails with the TO field Team_DistributionList@domain.com.
The problem with this is if you were to look at the .'[To]' property of this email, it is not as simple as "Team_DistributionList@domain.com". It is some long, crappy text that is not very readable. I have had to bypass these and use alternative methods to narrow them down.
These emails originally came from a Power Automate Web Flow. The email result is built by getting the User Profile email account string and turning that into a variable. That should just be a normally formatted string, tho, right?
Any suggestions for work arounds? This is really really frustrating me. LOL!
Troubleshooting guide:
If your Retrieve email messages Flow action is not retrieving anything at all and fails upon running there's something behind the scenes that's gone sour. PAD does not store all of its necessary tidbits on the machine running the PAD instance. PAD downloads the Flow from a server. If there's an issue with the stored PAD Flow you'll always pull out the same issue when running the Flow.
First try turning PAD on and off again.
Next try turning the machine on and off again, full reboot. Let it power down completely and then power back on after about 5 minutes of down-time.
If the issue persists, next try uninstalling/reinstalling PAD.
If the issue still persists, next try reviewing your Data Connections in your Office 365 account controls. Office Portal -> Power Automate -> Data -> Connections -> Create connection to Outlook
If the problem persists follow the below steps:
Create a new Flow from the PAD window. Name your Flow something useful. In your new Flow, create the following actions:
1. Launch Outlook
2. Retrieve email messages
3. Close Outlook
4. Display message w/ %RetrievedEmails% in the body text.
Set up your Retrieve email messages action to dispense every email in your inbox folder. In the Retrieve email messages action email filters options: "Mail folder:" should read "Inbox" (no quotes) for just inbox messages. If this does not work, you'll need to contact Microsoft support for more help. If this works, continue reading. Narrow your target down towards your goal. Mine is to get into a subfolder and retrieve particular emails based on some criteria. Next either target a subfolder "Inbox/yoursubfolder" or modify the "to contains", "from contains", etc, fields one at a time. Continue to run your Flow after each modification. If your Flow fails to retrieve anything with your particular needs, you will likely need to contact Microsoft support. If your Flow succeeds and your message box displays all of your desired information you've successfully overcome whatever hang-up was in your previous problem-Flow.
Once your new Flow is working as intended you can now open your problem-Flow and copy/paste the other Flow actions into/around the new Retrieve email messages Flow actions. Keep in mind however that changes to directory paths or file structure will need to be reflected in the Flow actions.
Hope this helps anyone. I've been battling this issue about 3 times now, each time it's a little more particular.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
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** 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. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) 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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages