502 bad gateway error but flow running succesfully

(0) Share

Report

Posted on by Hancha

101

Hi all,

I have a flow triggered from Powerapps, which creates:
a Team (Teams)

a Sharepoint item (data of the team)

several Sharepoint folders

online excel file in sharepoint

sends an e-mail with the excel link

Today I started receiving "FlowName.Run failed: error 502 bad gateway, message: the server did not receive response from an upstream server." (details in the attached picture)

NPI CReate team error message 20_09.PNG

However the flow run status is Success, and team is created as well as everything else...

What I´ve found though is that when I play the app (triggering the flow) from make.powerapps studio I get a powerapp runtime error on the flow triggering button/OnSelect:

NPI Powerapps flow error message.PNG

If I resubmit the flow the error disappears but returns once I play the app and select the button...
Any ideas?
Thanks for your help

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (1)

rrovira Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello, @Hancha!

Have you tried to resubmit your app? https://docs.microsoft.com/en-us/power-automate/fix-flow-failures#other-failures

Cheers!

Was this reply helpful? Yes No
Hancha 101 on at

Like (0)

Report
Copy link

Link copied!

Hello @rrovira,
that was one of the first things I tried:
Once I re-added the flow, the error in the app resolves itself but on the first run/button selection it is back....

not sure what you mean by re-submittin g of the app...

I also tried remove and re-added the trigger in flow but the result is still the same

Was this reply helpful? Yes No
Verified answer

Hancha 101 on at

Like (0)

Report
Copy link

Link copied!

Well,
I did not find any solution but a workaround:

The error was apparently caused by the flow response into powerapps parameter.
The response was supposed to tell me if a sharepoint item name already exists to avoid duplications (i.e. the first flow action was checking SP list duplications).
I removed that and started checking this in the powerapps itself via collection...
However I still wonder what and where the flow response hiccup was...

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

How long was the flow run? After less than 2 minutes (somewhere I read it was 90 seconds) I think the app assumes that there was no response

Was this reply helpful? Yes No
TKSHEP 212 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue, where you able to fix this issue? Any help would be greatly appreciated. Thank you!

Was this reply helpful? Yes No
juangonzalezAuc 101 on at

Like (1)

Report
Copy link

Link copied!

I've only encountered 2 reasons for this error:

1.- Your app is wating for the flow to finish and it takes close/over 120 seconds
2.- Your app is waiting for a response from the flow and the response can not be processed correctly by PowerApps (most likely type mismatch which I find creating a whole new var and adding the full flow response and examining said var)

Was this reply helpful? Yes No