The request failed. Error code: '502'. Error Message: 'BadGateway'. On Start and wait for Approval.

[kakis]

Hi everyone,

We have recently(2 months) started using D365 CE and all of our flows have been working perfectly since then.
Two days ago we installed Dynamics Marketing and we are now getting a Bad Gateway error on our start and wait for approval flows since then?
I don't really get how installing Marketing broke the approvals?

I have tried the following without any success:
Rebuilt the flow
Saved it as something else

Created a brand new simple approval flow with a manual trigger

Please note Approvals are working fine in all other environments. Is there anything i am missing?
Any Kind of help is appreciated!

Thank you

[bhawuks88]

There is a bug that the product team is working to fix. I think that this may be the root of your issue. 

Here is a workaround until the fix is released.

This workaround needs to be done by the Administrator of the environment.

To grant the "prvReadAsyncOperation" privilege:

1. 1. Go to Power Platform 
   2. Select Environments
   3. Select the environment in which the error occurs
   4. Select Security Roles > See All
   5. Click the ellipsis (...) next to Approvals Administrator and select Edit
   6. Search for "asyncoperation" (aka "System Job") table (select "Show all tables" if not visible)
   7. Update the read permission to "Organization"

[bhawuks88]

There is a bug that the product team is working to fix. I think that this may be the root of your issue. 

Here is a workaround until the fix is released.

This workaround needs to be done by the Administrator of the environment.

To grant the "prvReadAsyncOperation" privilege:

1. 1. Go to Power Platform 
   2. Select Environments
   3. Select the environment in which the error occurs
   4. Select Security Roles > See All
   5. Click the ellipsis (...) next to Approvals Administrator and select Edit
   6. Search for "asyncoperation" (aka "System Job") table (select "Show all tables" if not visible)
   7. Update the read permission to "Organization"

[bhawuks88]

There is a bug that the product team is working to fix. I think that this may be the root of your issue. 

Here is a workaround until the fix is released.

This workaround needs to be done by the Administrator of the environment.

To grant the "prvReadAsyncOperation" privilege:

1. 1. Go to Power Platform 
   2. Select Environments
   3. Select the environment in which the error occurs
   4. Select Security Roles > See All
   5. Click the ellipsis (...) next to Approvals Administrator and select Edit
   6. Search for "asyncoperation" (aka "System Job") table (select "Show all tables" if not visible)
   7. Update the read permission to "Organization"

[Anonymous]

We followed these steps to have the read permission on the Approvals Administrator role for the System Job in the customizations tab for your environment.

1. Sign in to the Power Platform admin center, select Environments in the navigation pane, and then select the environment.
2. Select Settings > Users + permissions > Security roles.
3. Select Approvals Administrator
4. Select Show all tables
5. Search for the "Customization" Section
6. Search for "System Job"
7. Set "Organization" for "Read" permission
8. Save

It could take some minutes to impact.

[AndiM]

Step 8: Don't forget to click the save button

[ethan37]

I just stumbled across this same Bad Gateway error. Does Microsoft have a timeline for solving this issue? Note, most users do not have the admin access to make the temporary changes noted above.

[leojar79]

Me funcionó gracias, saludos desde Colombia

[dev_paige]

Not everyone is able to get an administrator to fix things like this. Microsoft, please fix this bug ASAP. It has been an issue for years and hasn't been fixed. 

[Melinda]

@Soloadmin77 I had to open the table in Legacy View to see the item. So, if you go to Environments > Your Environment > Settings > Security Roles it gives you the option to go to legacy. Within Legacy, perform the same steps and you should see the System Job Role. 

[Chris]

Thanks, just to provide an update here: The product team has released a package that is updating the privilege.

Update the "Microsoft Flow Approvals" package to the latest version (2.0.4.7 or later) in the environment (please note that these actions need to be performed by an administrator):

1. Go to Power Platform Admin Center (admin.powerplatform.microsoft.com)
2. Select Environments
3. Select the environment in which the error occurs
4. Select "Dynamics 365 apps" (under Resources)
5. Look for the "Microsoft Flow Approvals" solution.  Its status should state "Update available".  Click the "Update available" link for this solution.
6. Check "I agree to the terms of service" 
7. Click "Update".

[dsecpa]

Unfortunately this doesn't fix the error for everyone.  My environment has the rights set correctly and still has the 502 error.

[RyanTan]

Does this update notification flows automatically to all admins? If the update is crucial and will affect major user, I think a proper notification to admins by Microsoft should be done.

[Chris]

Correct, a Message Center notification was sent to admins of affected tenants with ID MC679085.

[dynamiacs]

So the problem is already still alive...

try the settings with the permission for approval Admin . -> doesn´t work.

Flow Approval is on version 2.0.4.8 and still tells me installation failed and the workflow with approval steps runs into 502 bad gateway...

Need help

[rymacdow]

@dynamiacs  customizations to organizations can cause incompatibilities with the approvals solution.  502's can have many different causes and would require looking at your specific failures. Can you create a support case so we can look into your specific requests