'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Power Automate Approvers Not Receiving Notifications
Question details
Users need to resolve an issue where Power Automate approval requests fail to send Teams or email notifications when the requester is also an approver or manager.
- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Setting up or running automated approval workflows in Power Automate where the submitter is also listed as the approver.
- Observed behavior
- Ordinary form submitters trigger workflows correctly, but notifications fail to deliver via Teams or email when the requester and approver are the same person.
Verify your Microsoft 365 account permissions and ensure you have access to the Power Automate environment where the affected flow is currently running.
Resolve Tenant-Side Delays and Clear Cache
Use this method to fix temporary tenant connection issues by canceling pending runs and resetting your browser session.
Often, missing notifications are caused by a temporary synchronization delay on the Microsoft 365 tenant side rather than a broken workflow logic.
Navigate to your Power Automate dashboard, locate the affected flow, click into its run history, and cancel any currently hanging or failed runs.
Log out of Microsoft 365, clear your web browser's cache and cookies, and restart the browser to refresh your active session.
Trigger a new approval request and wait 15 to 30 minutes, as tenant-side delays can temporarily hold notifications before delivering them to Teams or Outlook.
Contact Microsoft 365 Support
If resetting the flow and waiting does not resolve the issue, the tenant connection may require backend support from Microsoft.
Looking for a Seamless Office Alternative? Try WPS Office
While troubleshooting Microsoft 365 tenant issues can be time-consuming, your document management shouldn't be. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for your daily productivity and approval tracking needs.
- 1. Download WPS Office: Visit the official WPS website and download the free installer for your operating system.
- 2. Install and Launch: Run the setup file and open WPS Office to access Writer, Spreadsheet, and Presentation.
- 3. Open Microsoft Formats: Directly open your existing .docx, .xlsx, or .pptx files to seamlessly continue your work.
Frequently Asked Questions
Why do approval notifications fail only when the requester is the manager?
Power Automate can experience logic loops or tenant-side delays when the submitter and the approver share the same identity, especially in 'First to respond' scenarios.
How long should I wait for delayed Power Automate emails?
Tenant-side delays usually resolve within 15 to 30 minutes. If notifications still do not appear in Microsoft Teams or Outlook after this period, an admin support ticket is recommended.
Does clearing the browser cache fix Power Automate backend issues?
While it doesn't fix backend servers, clearing the cache resolves stale session tokens that might prevent your local dashboard from triggering the flow correctly during testing.
