Set Run-Only User Connections Properly
Go to the flow in Power Automate portal > Details > Run only users
Set all connectors (especially Approvals and SharePoint) to use the manager’s connection (owner’s connection) or a shared service account connection that all users can run under.
This ensures the flow executes under the owner’s permissions, not the original creator’s.
2. Avoid Personal Connections for Critical Flows
Create and use service accounts or shared connections for flows, especially those that trigger approvals across hierarchy or involve multiple users.
This prevents dependency on your personal connection and avoids connection breaks if you leave or lose access.
3. Reassign Approval Assignments
Check the approval action’s Assigned To field — ensure it targets users who have permission and are in the same tenant.
If approvals are sent to external users, approval response might not trigger flow completion correctly.
4. Check Approval Response Configuration
In the approval action "Start and wait for an approval," verify that Response options and Timeout settings are correctly configured.
If the EM approved outside expected response options or if the flow times out waiting for approval confirmation, it might stop mid-flow.
5. Enable Flow Run History and Diagnostics
In Power Automate, review the Run History for the specific flow runs that got stuck.
Look for detailed error messages or status stuck on approval.
Add Configure Run After with error or timeout handling to gracefully handle approval issues.
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
Regards,
Riyaz
