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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Update SP list field t...
Power Automate
Suggested Answer

Update SP list field to "Emailed" if email sent or "Failed" if email not sent

(1) ShareShare
ReportReport
Posted on by 24
I have a SharePoint list that is populated from MS Form submissions.
My Power Automate flow is configured to send an email to the email address of the submitter (Email Address column) when their status (Status column) is changed to Eligible. This is working successfully, however, I would now like to add a step to that flow that will update a field to "Emailed" (Email Sent column) if the email is sent successfully, or "Failed" if the email is not sent successfully. Do I just add a Condition following my Send an email (V2) step? I have attached screenshots of all steps so far. Any assistance here would be greatly appreciated.    
Categories:
I have the same question (0)
  • Suggested answer
    chiaraalina Profile Picture
    2,425 Super User 2026 Season 1 on at
    Hi
     
    Here the reliable way is not a plain Condition after Send an email (V2). Because if Send an email (V2) fails, the flow usually stops there and never reaches the next normal step.
     
    Use this pattern instead:
     
    1. Keep Send an email (V2) where it is.
    2. Add an Update item action right after it to set Email Sent = Emailed.
    3. On that Update item action, use Configure run after so it runs only when Send an email (V2) is successful.
       
    4. Add a second Update item action to set Email Sent = Failed.
    5. On that second Update item, use Configure run after so it runs when Send an email (V2) has failed, timed out, or is skipped.
    So the logic becomes:
    If email sends successfully -> update SharePoint column to Emailed
    If email does not send -> update SharePoint column to Failed
     
    Let me know if it helped/worked.
  • Suggested answer
    11manish Profile Picture
    3,333 on at
    In Microsoft Power Automate, you should not use a Condition after the email step to check success or failure.
     
     Use “Configure Run After” on the next steps:
    •  If email is successful → update Email Sent = "Emailed"
    •  If email fails → update Email Sent = "Failed"
    The email action does not return a simple success value, so Run After is the reliable way to handle outcomes.
  • Amanda_S Profile Picture
    24 on at
    Thank you for the quick response!
     
    I have updated my flow (attached). The successful email is working correctly, but the failed email is not. Both are updating to "Emailed" in my SP list, even when an email is coming back undeliverable. Thoughts?
     
    Thanks again! ☺️
  • Suggested answer
    Haque Profile Picture
    3,653 on at
    Hi
     
    If really it failes that @11manish suggested, you can follow a different route. Once I used that @chiaraalina has suggested, that is very helpful. That process can store log so that you can confirm which email was sent and whic not. 
     
    I am stressing @chiaraalina's suggestion - adding one more point.
    So the logic becomes:
    If email sends successfully -> update SharePoint column to Emailed
    If email does not send -> update SharePoint column to Failed
     
    You do the above plus make a filter to rertieve only those item who's status are "Failed" or "New"
     
    So your SP list will have 3 states: New (you mark it when new item is created in the list), Emailed(MailSent), Failed (MailSentFailed). When you sen emial, just pick (New and Failed) items.
     
     

    I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!
     
  • Amanda_S Profile Picture
    24 on at
    I tried branching the Update Items as well, but they both return the same update of Emailed, even when one of the emails is undeliverable. 
     
    @chiaraalina, any suggestions to try to make this flow work correctly?
     
    Thanks again!
    Amanda
  • Suggested answer
    chiaraalina Profile Picture
    2,425 Super User 2026 Season 1 on at
     
    From your screenshot is see it is almost correct.
     
    But try this (real branching):
     
     
    The two Update item actions are configured as alternative outcomes of the same step, Send an email (V2).
    Update item runs when the email step succeeds
    Update item 2 runs when the email step fails / is skipped / times out
    So only the branch that matches the result of Send an email (V2) will run. That is the right way to handle success vs failure.
     
    Let me know if it worked!
  • Suggested answer
    Haque Profile Picture
    3,653 on at
     
     
    Let's fix the branch first: if you configure these two options (is successful and has failed) you don't need to have a check branch in step-4 (in your attached document!)
     
     
     
    You don't need the (question marked) condition - please follow @chiaraalina's post ( 04 Apr 2026 at 13:49:14).
     
     
    Also, can you please evaluate the comparison? Let's follow the steps below for boolean expression.
     
    Boolean declaration directly on the Value field, please see below:
     
    600
     
    Can you please type boolean value true or false in the expression window [green squred marked belwo] like below?
     
     
    If you see the declaration below (code view) it becomes a formula deaclaration and PA evalueates it correctly as comparion.
     
     
     
     
     
    Please check every where where we have Boolean value evaluated, make sure we typed the value through expression window. Power Automate doesn’t evaluate hand-typed Boolean value expression in any condition – bring them via Expression window, whatever “true” or “false”, they must be @true and @false in the code view.
     
     
     

    I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!
     
     
  • Amanda_S Profile Picture
    24 on at
    Thanks for the response, @chiaraalina!
     
    I did try the branching as I mentioned in my previous post, but I got the same result. Here's a screenshot of that branching.
     
  • Amanda_S Profile Picture
    24 on at
     
    I'm still trying to get this flow to work. If anyone has any suggestions, I'd greatly appreciate the assistance. 💜
     
     
    Thanks so much!!
    Amanda
     

     

  • Suggested answer
    Haque Profile Picture
    3,653 on at
    Just one more time, can you please post the two update action's setting side by side? Just to be confirmed, you have configured two update actions with these two separate actions:
    • "Emailed": Configured to run after successful email send (Configure run after: is successful).
    • "Failed": Configured to run after failure (Configure run after: has failed).
     
    By the way -  you have two more choices left to be implemted:
    1. Use Scope or Parallel Branches: You can place the email action inside a Scope and then use run-after on subsequent actions to branch based on success or failure.
    2. Try-Catch Pattern: Use a Scope for the email action and a parallel Scope for error handling, then update the SharePoint list accordingly.

     

     


    I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard