502 bad gateway error but flow running succesfully

[Hancha]

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)

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:

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

[rrovira]

Hello, @Hancha!

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

Cheers!

[Hancha]

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

[Hancha · Accepted solution]

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...

 

[Juan_Gonzalez]

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