Flow run failed : BadGateway

(1) Share

Report

Posted on by NBahmet

Hello, today I experienced an issue when all my flows that use "Run Excel Script" action stopped working.

They het int retry loop and flow fails after 8 retries. Flows where perfectly working before.

Also when trying to edit flow I can't choose script from dropdown.

Here is response from Run Script Action:

Also full message:

"Unexpected failure in request to Substrate\r\nclientRequestId: d656c71f-ce77-4461-bc75-b9ebc1e57834"

Thank you for help!

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (1)

NBahmet 23 on at

Like (0)

Report
Copy link

Link copied!

Raw outputs in case anyone needs them :
{
    "statusCode": 502,
    "headers": {
        "Access-Control-Expose-Headers": "Version",
        "mise-correlation-id": "b1c86c4c-d2dc-49f3-a175-3d9124c82e07",
        "x-ms-workflow-name": "c12d6925-63bc-4e8d-9c37-ff79b8a34d44",
        "Version": "3.6",
        "x-ms-client-request-id": "d656c71f-ce77-4461-bc75-b9ebc1e57834",
        "x-ms-datasourceerror": "True",
        "x-ms-request-id": "d656c71f-ce77-4461-bc75-b9ebc1e57834",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Content-Type-Options": "nosniff",
        "X-Frame-Options": "DENY",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "false",
        "x-ms-apihub-obo": "false",
        "Cache-Control": "no-store, no-cache",
        "Date": "Tue, 21 Feb 2023 22:33:30 GMT",
        "Content-Length": "380",
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "code": 502,
            "source": "flow-apim-msmanaged-na-eastus2-01.azure-apim.net",
            "clientRequestId": "d656c71f-ce77-4461-bc75-b9ebc1e57834",
            "message": "BadGateway",
            "innerError": {
                "message": "Unexpected failure in request to Substrate\r\nclientRequestId: d656c71f-ce77-4461-bc75-b9ebc1e57834",
                "storageErrorCode": 1
            }
        }
    }
}

Was this reply helpful? Yes No
jiwhite 500 on at

Like (1)

Report
Copy link

Link copied!

This looks like server errors across a region with Run Script and flows. I'm getting BadGateway errrors, too, from flow-apim-msmanaged-na-eastus2-01.azure-apim.net. It also appears to involve excelonline-cus.azconn-cus-001.p.azurewebsites.net. I can't even save flow updates.
https://powerusers.microsoft.com/t5/Using-Flows/Repeated-BadGateway-Errors-in-Run-Script-and-Saving-Flow/m-p/2027024#M37016

Was this reply helpful? Yes No
Coffee1231 6 on at

Like (2)

Report
Copy link

Link copied!

I'm getting the same issues and at a critical time.

Was this reply helpful? Yes No
Verified answer

NBahmet 23 on at

Like (2)

Report
Copy link

Link copied!

This morning it worked. So if you will encounter similar issue in the future - just wait 😅

Was this reply helpful? Yes No
jiwhite 500 on at

Like (1)

Report
Copy link

Link copied!

Yes, mine are working now, too.

Was this reply helpful? Yes No
spmofulton 66 on at

Like (0)

Report
Copy link

Link copied!
@NBahmet @jiwhite

So I kind of recognize the code from working way... way too much with open source equivalents to power Automate. I would strongly recommend share those logs with your IT and microsoft account manager

That 502 message is an outage message.

Those look like Azure connection/gateway issues rather than an issue with power automate. Since your service worked before this issue there are three causes:
Someone in your IT organization was upgrading a firewall or another system was upgrade and no one thought to inform end users to hey not use the network. People who are good in IT often don't have the best social skills. People in IT tend to push to production at inconvenient times all the time.
There was an outage of your Microsoft Azure, it is important that your IT and account manager be aware that you were affected. This way the vendor (Microsoft) can handle outages better.
There was an outage at your organization the standard SLA for outages that require no response or warning is twice the restart time window for your virtual machines or server. For even the smallest government in the united states that is no longer than 30 minutes before they need to inform users

Was this reply helpful? Yes No
jiwhite 500 on at

Like (0)

Report
Copy link

Link copied!

BadGateway errors are fairly frequent. They typically represent Microsoft doing maintenance or a failure in their cloud servers and they are not proactive in letting anyone know when there is an issue. These are all reports from different organizations. It has nothing to do with our installations. This was specifically a breakdown in whatever Microsoft process is governing Run Script connectors.

Was this reply helpful? Yes No