How to fix: 'b35af702-e802-42b3-8d49-f0ed3d12b879'

Question

I receive an “Encountered internal server error from Azure Resource Manager” when trying to run a Power Automate workflow. The error appears consistently on the same flow. Tracking ID: b35af702-e802-42b3-8d49-f0ed3d12b879.

Answer 1

Hi @Pablo Camps

Thank you for reaching out to Microsoft Q&A.

The error “Encountered internal server error from Azure Resource Manager” indicates that the Power Automate flow request successfully reached Azure, but failed due to an unexpected backend issue within Azure Resource Manager (ARM) or one of its dependent services (such as SharePoint, Dataverse, or Storage). This type of error is typically platform-side and is not caused by a syntax or logic issue in the flow itself. It can occur due to transient service instability, connector backend issues, corrupted flow metadata, or expired/broken connection tokens. Since the error occurs consistently on the same flow, it strongly suggests a backend or metadata-related issue rather than a design problem. The provided Tracking ID is used by Microsoft to trace the failure in internal logs.

Refer below points to resolve this issue or this is the workaround:

Re-authenticate all connections used in the flow Edit the flow, open each connector, and reconnect or reauthorize it. These refreshes expired or broken authentication tokens that commonly cause ARM failures.

Check the Run History to identify the failing action Review the flow run history to determine the exact step where the error occurs. This helps confirm whether the issue is isolated to a specific connector or action.

Clone the flow and use the copied version (recommended workaround) Save a copy of the existing flow, disable the original flow, and enable the cloned one. This often resolves issues caused by corrupted flow metadata in Azure Resource Manager.

Retry the flow after some time If the issue is due to a transient Azure platform problem, it may resolve automatically once the backend service stabilizes.

Answer 2

The error message indicates an internal server error (HTTP 500–class) coming from Azure Resource Manager when the flow runs. These are typically transient service-side issues rather than configuration problems in the flow itself.

To address it for the specific flow:

1. Identify exactly where the flow fails:
   1. In Power Automate, go to My flows.
   2. Select the failing flow.
   3. In 28-day run history, open a failed run.
   4. Locate the action with the red exclamation icon and open it to review the detailed error message in the right pane.
2. Confirm the error code and retry:
   • If the action shows an HTTP 500 or 502 error, this is a temporary or transient failure.
   • In the run history, select Resubmit to rerun the flow with the same inputs.
3. Check connections and permissions:
   • Ensure all connections used by the failing action are authenticated and have the required permissions, as connection or authentication issues can also surface as runtime errors.
4. Add resilience to the flow:
   • Configure retry policies and error handling on the failing action(s) to better handle transient service issues.
   • For example, enable retries on the Azure-related action so that temporary Azure Resource Manager issues do not cause the entire flow to fail.

If the same action continues to fail with 500-class errors even after resubmission and proper authentication, the issue is likely on the Azure service side and may require investigation in Azure (e.g., checking the target resource, region, or service health) or opening a support ticket with Microsoft, providing the tracking ID and run details.

---

References:

• Troubleshoot a cloud flow
• Troubleshoot cloud flows
• Flow Runtime errors and recommendations