Overview
Debugging Power Automate flows is essential for identifying errors and optimizing workflows. Run History is a built-in feature that helps track execution details, identify failures, and troubleshoot issues.
View each flow execution in detail
Identify failed steps and error messages
Check input/output data for each action
Resubmit failed flows after fixing errors
1️⃣ Accessing Run History in Power Automate
Steps to View Run History
1️⃣ Go to Power Automate Portal: https://make.powerautomate.com
2️⃣ Click “My Flows” from the left panel
3️⃣ Select the flow you want to debug
4️⃣ Click on the “Run History” tab
5️⃣ Select a specific run to view detailed execution logs
Tip: Runs are categorized as Succeeded, Failed, or Running for easy filtering.
2️⃣ Understanding Run History Details
When you open a specific flow run, you will see:
Trigger Details – How the flow started and input data
Execution Timeline – Duration of each step
Action Details – Input, output, and status of each step
Error Messages – If a step fails, you will see a detailed error description
Example: If a flow fails at the “Send Email” action, you can check whether:
- The recipient email was invalid
- The SMTP service was down
- Authentication failed
3️⃣ Debugging Common Power Automate Flow Errors
🔹 1. Trigger Not Firing
Issue: The flow doesn’t start as expected.
Solution:
✔️ Verify trigger conditions (e.g., SharePoint list updates, email arrivals)
✔️ Check connections & permissions
✔️ Confirm data meets trigger conditions
🔹 2. Action Failed with Error Message
Issue: A step in the flow fails.
Solution:
✔️ Click on the failed step to view error details
✔️ Check input/output values
✔️ Resubmit the flow with correct data
🔹 3. Flow Takes Too Long to Execute
Issue: The flow runs for an extended time.
Solution:
✔️ Optimize loops and unnecessary actions
✔️ Use parallel execution instead of sequential steps
✔️ Reduce API calls (e.g., batch processing for SharePoint updates)
🔹 4. “Action Timed Out” Error
Issue: API calls take too long and cause a timeout.
Solution:
✔️ Check API rate limits
✔️ Use retry policies
✔️ Reduce external dependencies
🔹 5. Authentication & Permission Issues
Issue: The flow cannot access a required service.
Solution:
✔️ Re-authenticate in Connections
✔️ Ensure the flow owner has the right permissions
✔️ Check Data Loss Prevention (DLP) policies
4️⃣ Using Retry, Timeout, and Error Handling in Power Automate
Enable Retry Policy for Actions
If an action fails due to a temporary issue (e.g., API timeout), enable automatic retries:
1️⃣ Click on the action → Settings
2️⃣ Enable Retry Policy
3️⃣ Choose Exponential Retry to attempt again with delays
Example: If an API call to SharePoint fails due to network issues, Power Automate will retry before failing completely.
5️⃣ Resubmitting a Failed Flow Run
If a flow run fails, you can manually resubmit it after fixing the issue:
1️⃣ Open the failed flow in Run History
2️⃣ Click “Resubmit”
3️⃣ Modify inputs if needed
4️⃣ Monitor the new execution log
Example: If a flow failed due to a missing approval, resubmitting will send the approval request again.