Troubleshoot a cloud flow

This article contains tips and tricks for troubleshooting cloud flows. With the new designer, you can easily find and fix errors using Copilot. Check out the video in this article in the Troubleshoot in Copilot section.

Identify specific flow runs

Once you build and deploy your flows, you might need to debug specific flow runs to confirm that your flow ran as expected. By default, the flow owner can look at the Start, Duration, and Status columns in the run history view in Power Automate to help them identify the flow run they're interested in debugging. The owner can also expand the troubleshooting section to identify the specific run in which they're interested, however, for flows that run frequently, this can be time-consuming.

To make it more efficient to identify flow runs when debugging, Power Automate provides the ability for flow owners to configure the list of columns that displays on the run history page for each flow run. These columns map to the trigger outputs for your flow. When you display the columns you want, you save time since you see the relevant columns by default on the run history view.

Follow these steps to add one or more columns to your run history view.

1. Sign in to Power Automate.

2. On the left side of the screen, select My flows.

3. Select the flow for which you want to get more details.

4. On the flow details page, select Edit columns.

5. Select the columns that you want to add to your run history view for the flow that you selected, and then select Save.

6. View the list of columns that displays on the run history view for the flow you selected.

   The hasAttachments and isHTML columns are now visible for the flow so that you can quickly see those values to help you debug the flow.

   

Tip

You can also configure the list of columns that displays with the All runs view.

Repair tips in email

Repair tips are sent to flow owners via email whenever a cloud flow fails. These repair tips emails contain specific, actionable feedback about certain errors. For example, one common error is setting up a cloud flow that attempts to get a person’s manager in Office 365—but there's no manager configured in Microsoft Entra ID. If this or several other conditions cause your flow to fail, you get a repair tips email.

The repair tips email contains the following sections:

Name	Description
Time	Displays the time the flow first failed.
What happened	Provides a description of the problem that caused the failure in the flow.
How do I fix	Provides tips for resolving the issue that caused the failure in the flow.
Troubleshooting tips	Provides details including the number of times the flow failed, and a link to retry the flow with the same input data.

To fix the reported errors, select Fix my flow and follow the steps in the repair tips email.

Repair tips emails are optional. If you don't want to receive them, turn them off from the properties menu for the specific flow.

If your flow fails, you can also troubleshoot it directly in Power Automate. Here are some common failure scenarios and tips on how to fix them.

Identify the error

Follow these steps to find the error and learn how to fix it,

1. Select My flows.

2. Select the flow that failed.

3. In the 28-day run history section, select the date of the failed run.

   Details about the flow appear, and at least one step shows a red exclamation icon.

4. Open that failed step, and then review the error message.

   On the right pane, you can see the details of the error and how to fix it.

   

Authentication failures

In many cases, flows fail because of an authentication error. If you have this type of error, the error message contains Unauthorized or an error code of 401 or 403 appears. You can usually fix an authentication error by updating the connection:

1. On the right pane below How to fix, select View Connections.

2. Scroll to the connection for which you saw the Unauthorized error message.

3. Next to the connection, select the Fix connection link in the message about the connection not being authenticated.

4. Verify your credentials by following the instructions that appear.

5. Return to your flow-run failure, and then select Resubmit.

   The flow should now run as expected.

Conditional Access and embedded flow authentication errors

If your flow works from the Power Automate portal but fails with an authentication error when users access it from SharePoint, Microsoft Teams, or Excel, the issue might be a Conditional Access (CA) policy mismatch.

Symptoms

• Users see an authentication error when they try to view or run a flow from a SharePoint list, a Teams channel, or an Excel workbook.
• The same flow works correctly when accessed directly from make.powerautomate.com.
• Your organization has Conditional Access policies that require multifactor authentication (MFA), Terms of Use acceptance, or device compliance.

Cause

When a flow is embedded in another Microsoft 365 application, the host application performs a token exchange with Microsoft Flow Service to authenticate API calls. If your CA policies have different requirements (MFA, Terms of Use, or device compliance) for the host application and Power Automate, the token exchange fails.

This typically happens when CA policies target individual applications with different requirements, rather than using the Office 365 app or All cloud apps target.

Additionally, if a CA policy includes a Terms of Use grant control, existing flow connections can break retroactively because the silent token refresh can't present the Terms of Use acceptance page.

Resolution

1. In the Microsoft Entra admin center, go to Protection > Conditional Access > Policies.
2. Switch your policy to target the Office 365 app or All cloud apps. This ensures consistent requirements across Power Automate and the apps that embed it.
3. If you must target individual apps, verify that Microsoft Flow Service (Application ID: 7df0a125-d3be-4c96-aa54-591f83ff541c) is included alongside the host applications (SharePoint, Teams, Excel) with matching requirements.
4. If your policy includes Terms of Use, exclude service accounts and dedicated flow connection owners from that policy. Flow connections refresh tokens silently and can't accept Terms of Use interactively.

After updating policies, affected users must sign out and sign back in for the changes to take effect.

For more information, see Conditional Access and multifactor authentication in Power Automate.

Troubleshoot in Copilot

The troubleshoot in Copilot feature in Power Automate can assist you in identifying and resolving errors that might occur during the testing of cloud flows or when reviewing flow run history. You can use this Copilot feature when the new designer experience is enabled.

Learn how to troubleshoot cloud flow errors with Copilot in this quick video:

The troubleshoot in Copilot feature provides a human-readable summary of the error and, when possible, attempts to provide a solution to correct the error. This can greatly enhance your experience by reducing the time and effort required to troubleshoot and resolve issues.

Note

The troubleshoot in Copilot feature might not work in all scenarios. It’s continuously learning and improving over time, which means its ability to assist users and resolve issues only gets better. This is a great example of how AI and machine learning can be leveraged to improve your experience and productivity.

Action configuration

Flows also fail if a setting in an action of the flow doesn't function as expected. In this case, the error message contains Bad request or Not found, or an error code of 400 or 404 appears.

The error details should specify how to correct the failure. To update the configuration:

1. Select Edit and then correct the problem inside the flow definition.
2. Save the updated flow.
3. Select Resubmit to try the run again with the updated configuration.

Other failures

If the error code 500 or 502 appears, the failure is temporary or transient. To try the flow again, select Resubmit.

Related information

Training: Best practices for error handling in Power Automate flows (module)