502 bad gateway

[SandraTeh]

Hi,

I have a flow that I set up few months ago. However, it failed recently giving an error messge of BadGateway.

Interestingly, all my previously history are gone except those that fail.

How do i resolve this?

Thank you

Sandra Teh

[v-yamao-msft · Accepted solution]

Hi @SandraTeh,

The run duration limitation for flow is 30 days. And max run history retention is 28 days. Your flow was created a few months ago, I am afraid that it has run out of limitation.

Please check the doc for more details:

https://docs.microsoft.com/en-us/flow/limits-and-config

Bad gateway means that the failure is temporary or transient, please try to resubmit the flow. If you are still having the issue, please try to recreate the flow to see if it will work.

Best regards,

Mabel Mao

[SandraTeh]

Hi,

I created a new flow, deleted the old one and it is now working again.

[Gaelle]

Hello @v-yamao-msft !

Unfortunately, your answer is not pleasant :

I have a flow with a lot of actions, nested in conditions or loops.

I can not redo everything the second flow decides to launch a 502 error.

I read somewhere (on this forum's threads mostly) that it could be caused by upgrades from MS Flow. Could you notify the dev team to do something ? Because for me it is a bug.

To avoid me the boring and long task to recreate my flow from scratch, I tried to export and import it, but it still prompts a 502 message.

Do you have any idea of a workaround please ? 

Thanks a lot.

Have a nice day.

[Anonymous]

I agree this is not an acceptable process. The issue is with Microsoft and a fix should be made. It should not be expected that users have to recreate their flows every time this error occurs.

[NoodleMan]

Agreed! MSFT should release a fix to solve the issue. Expecting users to re-produce all flows are not practical. 

[dc932]

Agreed... I have very complex flows that are in production and rebuilding from scratch can cause room for error. This wouldn't allow me to rerun jobs either that has failed on the broken flow... Please provide better solution.

[Julien1]

+1 same error, seems like not much has been done in 3 years

[SzS]

and still this problem after import

[drewbty]

Same issue here, some flows sporadically failing every few days with 502 'Bad Gateway'. Completely random. Boy have my eyes been opened up of how amateur Microsoft are since we moved onto Power Automate. So unacceptable to just say it's a 'transient issue' and not fix things...even years later

[kudorje]

@v-yamao-msft  : What is the solution apart from having your customers re-do their work from scratch even though this wasn't user generated issue? We are still having this issue spur up and user adoption with these kinds of issues are negatively impacted. Does MSFT care about this? The error message of simply saying Bad gateway isn't enough to decode to learn the cause of the error.

[ebergmangca]

Same issue here. Completely randomly, my workflow stopped working this morning when it has been working fine daily for almost a year. I tried to recreate the flow and even that didn't work. The connection to Teams is not working and I cannot select a Post in option. Error below. Something about geo 'unitedstates'.

Could not retrieve values. The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The ApiHubsRuntime API call failed with http status code 'BadGateway' and response content '{
"error": {
"code": 502,
"source": "power-apis-usgov001-public.azure-apihub.us",
"clientRequestId": "6be05b83-0539-4c44-9d05-f16fce395302",
"message": "BadGateway",
"innerError": {
"error": {
"code": "InternalServerError",
"message": "Http request failed with unhandled exception of type 'InvalidOperationException' and message: 'Could not find endpoint for geo 'unitedstates'.'."
}
}
}
}'
at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_1`2.<<CallService>b__0>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 636
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__47`2.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 493'.