cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ShineTan123
Helper V
Helper V

Action 'Send_an_email_(V2)' failed. Parameter 'To' cannot be null or empty.

Hi Everyone,

 

I encountered a very strange problem.

 

I am building a flow from sharepoint list for users to submit request and get approval. Since the approver delegation is very complicated, which I cannot combine the request and approver delegation into the same flow because it will be more than the allowed maximum 8 nesting. Thus I firstly create a flow to complete the approver delegation then use the update item function to write back to the sharepoint list for approver of each step. The approver delegation flow works well.

 

However, the question is on the subsequent flow for sending email, it is always failed, saying "To" is null and empty. I have tried recreating, but still failed, so I don't know what to do. Appreciate if anyone can help me out.

ShineTan123_1-1647404119245.png

 

ShineTan123_0-1647404097172.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
KvB1
Solution Sage
Solution Sage

After the delay, add a new action: fetch sharepoint item. Use the same site and list as in the trigger. You need to add an id, use the dynamic content id of the trigger

 

Use the dynamic content mail column of the fetch sharepoint item action to populate the 'to' field, instead of using the dynamic content mail column of the trigger

View solution in original post

20 REPLIES 20
fchopo
Super User
Super User

Hi @ShineTan123 

Can you share your workflow in the "send an email action" ? Which value are you using in the "To" parameter?

Regards,

Ferran

Did I answer your question? Please consider to mark my post as a solution to help others.
Proud to be a Flownaut!
KvB1
Solution Sage
Solution Sage

whats in the condition, and what are you using as input for who to send the mail to?

Hi @fchopo 

"To" parameter is using dynamic content. This dynamic input is actually the output from the other flow.

I built the other flow to decide which should be the approvers, then it write back to sharepoint list under the name that I am using in the "To" dynamic content.

 

ShineTan123_0-1647419643450.png

 

Hi @KvB1,

Under the condition there are a lot of steps, but basically is to send email and request for approvals. And now the error stops the flow at the very beginning of the condition.

"To" parameter is using dynamic content. This dynamic input is actually the output from the other flow.

I built the other flow to decide which should be the approvers, then it write back to sharepoint list under the name that I am using in the "To" dynamic content.

ShineTan123_1-1647419885612.png

 

KvB1
Solution Sage
Solution Sage

Can you verify that the 'to' field is populated by the correct value?

Easiest way to do this is to create a compose action and give it the same value

Hi @ShineTan123 

Which is the "Spoc" data type field in SharePoint? Is it a a people column, or is it a text one? You should check the value of that column in SharePoint, which is probably causing the error.

Regards,

Ferran

Did I answer your question? Please consider to mark my post as a solution to help others.
Proud to be a Flownaut!

Hi @fchopo,

I have thought about this part actually. In the sharepoint, the type of that field I created is Single line of text. And the output from the other flow is email address, thus I tried manually input the email address in the sharepoint list, and the flow can run successfully.

However, when I expect the writeback from the other flow, meaning leave the field blank and wait for the other flow to update, then the current flow failed with the error of null or empty. So I am thinking whether it's the constraint of Power Automate that one flow cannot use the output from the other flow, but the weird thing is it actually got successful few times, though most of the time got failure.

Hi @KvB1,

Would you mind demo on how to verify? I added the compose and input with this dynamic content, I don't know what does it mean.

ShineTan123_1-1647421228059.png

 

ShineTan123_0-1647421178296.png

 

KvB1
Solution Sage
Solution Sage

This will tell you exactly what is used in the send email action in the 'to' field

 

It's a way of troubleshooting

 

If you 'Click to download' it will show you what is being used as an address to send the mail to, and can see where you have to correct something

Hi @KvB1,

It's blank when I click download. Both input and output are blank. So meaning it's nothing in this dynamic content?

KvB1
Solution Sage
Solution Sage

Yes that is true, I guess that means its a sharepoint field thats empty?

Hi @KvB1,

In fact not empty. I also double clicked to check, the email is there.

 

ShineTan123_0-1647422056613.png

 

KvB1
Solution Sage
Solution Sage

Very strange problem. Earlier you described an interaction with another flow. The other flow populates this email field during the delay in this flow, correct?

But this causes this flow to fail.

 

If you run it solo and manually fill in the email field, it doesn't give the error, right?

The only possibility seems that the field wasn't filled by the other flow at the time the delay passed. If the other flow doesn't give any errors (by trying to fill a text field with an array or something), I guess this flow will execute the send mail action before the other flow has finished populating the necessary fields?

Hi @KvB1,

I have also tried to test whether is about the timing.

The correlated flow and this flow has the same trigger, "when item is created".  I put 5mins delay in this flow, the correlated flow is run less than 1min with no error. but when the delay passed, the error still come. I also suspect whether the sharepoint is not refreshed, so I immediately refresh after the correlated flow completes and I can see the field populated successfully. But this flow still failed, so my hands are tied.

KvB1
Solution Sage
Solution Sage

Ah okay, that explains it then

 

The dynamic content for the email field is from the trigger in the flow that fails, correct?

The delay is irrelevant, because the information that will be used for the email field was grabbed at the trigger stage, not at the send email stage.

 

The quick and dirty way that would fix it: store the ID of the trigger item in a variable, then after the delay fetch this item again, using the ID stored in the variable. Use the email field of that output of that action to populate the 'to' field in the email

Hi @KvB1,

Could you explain how I should do that? Using the term in the power automate will be much appreciated.

KvB1
Solution Sage
Solution Sage

After the delay, add a new action: fetch sharepoint item. Use the same site and list as in the trigger. You need to add an id, use the dynamic content id of the trigger

 

Use the dynamic content mail column of the fetch sharepoint item action to populate the 'to' field, instead of using the dynamic content mail column of the trigger

Hi @KvB1,

Do you mean "Get item"? If yes, where do I put id in?

 

ShineTan123_0-1647425423601.png

 

KvB1
Solution Sage
Solution Sage

This is a different action: Get itemS

 

You need: Get item (without the s)

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

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.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (6,177)