Send & Receive Issues

Fix Power Automate Flow Succeeds but Email Not Delivered

Steve KSteve K Oct 21, 2026 869 views

Question details

Users need to resolve an issue where a Power Automate flow successfully completes an email sending action, but the recipient never receives the message.

How to Fix Power Automate Flow Succeeds but Email Is Not Delivered
Product
Microsoft Power Automate
Device & OS
not provided
Scenario
Running an automated workflow that utilizes the 'Send an email notification (V3)' action to distribute alerts or documents.
Observed behavior
The flow's run history shows the email action as 'Succeeded', but the email does not appear in the intended recipient's inbox due to connector issues, filtering, or downstream server rules.
Before you start

Ensure you have access to the Power Automate run history for the affected flow and permissions to view Exchange Online message traces if administrative tracking is required.

Solution 1Recommended

Verify Run Details and Exchange Server Mail Flow

Check the exact inputs used during the flow run and rule out local mailbox filtering or server-wide blocking.

Power Automate only confirms that the email was handed off to the Exchange server. Downstream factors like typos in the address, aggressive junk filters, or Exchange mail flow rules can silently drop the message before it reaches the inbox.

1
Inspect the Run History

Navigate to 'My flows' in Power Automate, click your flow, and open the specific Run history. Expand the 'Send an email notification (V3)' action to verify the exact recipient email address and ensure no errors are in the outputs.

2
Check Local Inbox Rules and Junk Filters

Ask the recipient to check their Junk Email folder, Quarantine, and active Inbox rules to ensure the automated email wasn't automatically moved or deleted upon arrival.

3
Perform an Exchange Message Trace

If you have administrator privileges, go to the Exchange admin center and run a Message Trace using the sender and recipient addresses to see exactly where the email was routed or dropped after Power Automate handed it off.

Verify Run Details and Exchange Server Mail Flow
Free Microsoft Office alternative

Need a Reliable Office Suite for Your Workflow Attachments?

While troubleshooting Power Automate email delivery issues, you might need a fast, dependable office suite to open, review, or create the document attachments used in your automated workflows. WPS Office is a powerful, free alternative to Microsoft Office that easily handles all your document needs.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the Software: Run the downloaded installer and follow the quick on-screen instructions to set up the suite.
  3. 3. Open Your Workflow Documents: Launch WPS Office to instantly view, edit, or create Microsoft Office compatible documents seamlessly.
Fully compatible with Microsoft Office formats like .docx, .xlsx, and .pptx.Lightweight application that uses minimal system resources and loads quickly.All-in-one workspace offering Writer, Spreadsheet, Presentation, and PDF tools.Familiar, intuitive user interface that requires zero learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Power Automate report the email action as successful when it wasn't delivered?

A 'Succeeded' status in Power Automate simply means the application successfully handed the message data over to the email server (Exchange). It does not track what the server does with the email afterward, such as blocking it due to spam filters or delivery rules.

What is the difference between V2 and V3 email connectors in Power Automate?

The V2 and V3 connectors use different background APIs and authentication methods to process email sending. Occasional platform updates or permission changes can cause one version to experience delivery issues while the other continues functioning normally.

How do I access the Run History for my Power Automate flow?

Log into Power Automate, navigate to 'My flows' on the left menu, and click on the name of the flow you want to investigate. On the flow details page, look for the '28-day run history' section and click the start time of the specific run to view detailed action inputs and outputs.