Bad Gateway error 504 for Add new row to Excel

[zvc]

Hi!

I have a flow that adds a row to an excel sheet when a new email arrives in a shared mailbox. It was working well last week (when I made it) but suddenly it stopped working. The error that comes back is "Bad Gateway" and I've tried troubleshooting but can't figure it out. I've tried:

• Re-making the entire flow in a new flow
• Removing the Excel connection and redoing the flow
• Redoing the flow with a new target document

Neither of these have worked, but a separate flow which updates a column in a row that was created by the previous flow does work. So it seems like the issue is with the "Add row" action and not the Excel connector.

Does anyone have any ideas of how to fix this, or how to find out if it's a general outage?

[v-peijunz-msft]

Hi @zvc 

To better to clarify your issue, could you please share the screenshot of your flow, and also the error message you received?

Thank you.

Best regards,

Sylvia

[zvc]

Hi!

Absolutely! The message I receive is:

{
    "statusCode": 504,
    "headers": {
        "Pragma": "no-cache",
        "x-ms-datasourceerror": "True",
        "x-ms-request-id": "4d28aaf2-db05-468b-9470-46d6cc5bb46a;8db97a1d-fb0c-49fe-a2dc-262413f2fffb;d68ab1b7-c27c-4ed4-9b14-22d3805bb9fb;794abb33-90d2-4e8a-928a-1035ace86632;f2617e83-b7cb-46d6-9327-1227161f5298",
        "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": "Wed, 26 Apr 2023 06:53:43 GMT",
        "Content-Length": "727",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "error": {
            "code": 504,
            "source": "flow-apim-europe-002-westeurope-01.azure-apim.net",
            "clientRequestId": "57687a7f-bf0a-464f-b320-06c6355133f1",
            "message": "BadGateway",
            "innerError": {
                "status": 504,
                "message": "Request to Graph API has timed out.\r\nclientRequestId: 57687a7f-bf0a-464f-b320-06c6355133f1\r\nserviceRequestId: 4d28aaf2-db05-468b-9470-46d6cc5bb46a;8db97a1d-fb0c-49fe-a2dc-262413f2fffb;d68ab1b7-c27c-4ed4-9b14-22d3805bb9fb;794abb33-90d2-4e8a-928a-1035ace86632;f2617e83-b7cb-46d6-9327-1227161f5298",
                "error": {
                    "message": "Request to Graph API has timed out."
                },
                "source": "excelonline-we.azconn-we-002.p.azurewebsites.net"
            }
        }
    }
}

Error message

And the flow looks like this:

Flow

Thank you!

[zvc]

@v-peijunz-msft Do you have any ideas for how to solve this? 🙏

[nk9]

Same issue... anyone got an idea on fix?

[zvc]

I'm not sure what the issue was for me, but I made a new Excel and connected the flow to that and then everything worked again

[nk9]

I tried a new Excel, tried a new table in a new tab, no luck...

However, when I reduced the line items from approx. 500 to 100, it worked.

Everyone seems to find a non-standard way of making this work. Microsoft should get on top of this.