Power Automate The request failed. Error code: '502'. Error Message: 'BadGateway'.

(1) Share

Report

Posted on by AstroNorman

Hi,

I have an Approval flow that been running for more than a year.

Recently, the approval has failed with status code 502.

I have found people posting the same problem above in the last few days:

- https://powerusers.microsoft.com/t5/General-Power-Automate/I-cant-attach-an-a-file-in-Approvals-quot-BadGateway-quot-Error/m-p/2340541

- https://powerusers.microsoft.com/t5/General-Power-Automate/Power-Automate-The-request-failed-Error-code-502-Error-Message/m-p/2342435

- https://learn.microsoft.com/en-us/answers/questions/1363274/attachment-not-working-on-power-automate

502 error.PNG

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (1)

Sort by

sandeepstw 312 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi There,

The error code 502 usually indicates a "Bad Gateway" error. For an Approval flow in Power Automate, this can happen due to temporary issues with the service. You can do following things -
Start by attempting to manually trigger or run the failed flow instance again to see if the issue was transient. Review the Microsoft 365 admin center service health dashboard for any known issues with Power Automate or associated services. Analyze the specific step or action that failed within the flow for any additional error details or messages.

Please give kudos and mark as solution if it helps.

Thanks,

Was this reply helpful? Yes No
AstroNorman 15 on at

Like (1)

Report
Copy link

Link copied!

Hi @sandeepstw

All Power automate services are healthy according the admin health dashboard.

My errors and all the errors encountered by other user is related to Approval Attachment field.

Was this reply helpful? Yes No
sandeepstw 312 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi There,

If the error is specifically tied to the Approval Attachment field, consider the following solution. Ensure that the attachments being sent for approval aren't exceeding the size limits. The attachment size should be below the maximum threshold.
Sometimes, specific attachments might be corrupted or not fully uploaded. Ensure the integrity of these attachments before they are sent for approval.
Try adding a delay before the Approval action in your flow to ensure all previous actions have fully completed.Reconfigure the Approval action, ensuring all necessary fields are correctly filled out, especially the attachment field.

Please give kudos and mark as solution if it helps.

Thanks,
Sandeep Mishra

Was this reply helpful? Yes No
AstroNorman 15 on at

Like (0)

Report
Copy link

Link copied!

The per attachment max size limit configured is 10 MB in my environment.

The combined total size of all the attachments for 1 of my failing flow is 8 MB which is under Approval connector 50 MB limit.

I had raise a ticket to Microsoft Support. Thanks for the info though.

Was this reply helpful? Yes No
Verified answer

AstroNorman 15 on at

Like (0)

Report
Copy link

Link copied!

According to Microsoft Support, the issue is affecting Asia region.

Was this reply helpful? Yes No
b1324 17 on at

Like (0)

Report
Copy link

Link copied!

If you approval has attachments .. make sure to check this off in Admin Center -> Security Roles.

This worked fine for me as well for months now, but something just changed at MS last week and this broke until this fix here.

Was this reply helpful? Yes No
iAm_ManCat 18,256 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Hi, there was some information published about this on the 'Known issues' section of power platform admin portal, but this section is only currently available in the US.

Details for the problem and workaround until they resolve the issue are the following:

Problem

You might encounter a BadGateway, 502, XrmApiServerError, 'Request to XRM API failed', or 'Principal user is missing prvReadAsyncOperation privilege' error when creating an approval.

Workaround

We are working on a fix for this issue. In the meantime, you can resolve this issue by granting the "Approvals Administrator" role the missing privilege in the environment (please note that these actions need to be performed by an administrator).

To grant the "prvReadAsyncOperation" privilege:

Go to Power Platform Admin Center (admin.powerplatform.microsoft.com)

Select Environments

Select the environment in which the error occurs

Select Security Roles > See All

Click the ellipsis (...) next to Approvals Administrator and select Edit

Search for "asyncoperation" (aka "System Job") table (select "Show all tables" if not visible)

Update the read permission to "Organization"

Cheers,

Sancho

Was this reply helpful? Yes No