Prompt
Why are my Power Automate approvals stuck in pending
Latest observation
Nov 13, 2026
OpenAI APIWeb search: off
Power Automate approvals usually get stuck in Pending for one of a few common reasons. Here are the most likely causes and how to check them:
1) The approver hasn’t actually received or opened it
- Check the approver’s Approvals center in Power Automate.
- Also check their email, especially if they use Outlook/Teams notifications.
- Sometimes the request is there but buried in the Approvals app or Teams.
2) The flow is waiting on a response that never came
- If your flow uses Start and wait for an approval, it will stay pending until someone responds.
- If the approver never takes action, the flow remains paused indefinitely unless you add a timeout.
3) The wrong person or group was assigned
- Confirm the approval was sent to the correct email address.
- If assigned to a group, make sure someone in the group is expected to respond.
- If the approver left the company or has a typo in the address, it may never complete.
4) The approval action is failing silently downstream
- Open the flow run history and inspect the approval step.
- Check whether the approval was created successfully but the next step failed.
- A failed later step won’t usually keep the approval pending, but it can make it look like the process is stuck.
5) Environment or connector issues
- Connection to the Approvals connector may be expired or broken.
- Re-authenticate the connection in Power Automate.
- If your tenant has DLP or governance restrictions, approvals may be impacted.
6) Delays or sync issues in the service
- Sometimes approvals appear pending due to a temporary Microsoft service delay.
- Check the Microsoft 365 Service Health dashboard if you’re in an enterprise tenant.
- Refresh the approval center or wait a bit and check again.
7) The flow is missing a timeout/escalation path
- Without a timeout, an approval can remain pending forever.
- Add:
- a timeout on the approval action
- a reminder
- an escalation to another approver
8) The approver responded, but the response didn’t register
- This can happen if:
- multiple approval actions are being created
- the same approval is triggered twice
- the approver used an old email notification
- Check if there are duplicate runs or duplicate approval items.
What to check first
- Go to Power Automate > My flows > Run history
- Open the run
- Check the approval action:
- Was it created?
- Who was assigned?
- Is it still waiting for response?
- Ask the approver to check:
- Power Automate Approvals
- Outlook
- Teams Approvals
If you want to prevent this going forward
- Add a timeout
- Use escalation
- Send to a single user instead of a group if possible
- Confirm the approver’s identity dynamically from a reliable source
- Add notification reminders
If you want, I can help you troubleshoot it step-by-step if you paste:
- the approval action type you’re using
- what the run history shows
- whether it’s assigned to a person, group, or manager chain