Bad Gateway 504

[MoBrien]

Hi,

I have a flow that is a number of months old that has stopped running. I have a number of other flows which are copies of the original flow but link to different sources. These all continue to work as normal. I have created a new flow to recreate the original, it appears to fail at the same point. The flow is triggered by a new Forms submission. The flow looks like it collects the input information from forms but is unable to output the information to ExcelOnline using AddRow.

Can you please advise?

"statusCode": 504,

    "headers": {

        "Pragma": "no-cache",

        "x-ms-datasourceerror": "True",

        "x-ms-request-id": "7b1420e0-cc66-4735-ada4-b13e9e002ed5;964a6534-6530-45a4-b0c5-aedba347c019;aaf5f5f0-23d1-4018-8006-ae3a825dde8b;e5254fa9-62ee-415d-bcc2-de769d3ce467;87d02b6b-d4d7-4a77-b1a2-c0594279495a",

        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",

        "X-Content-Type-Options": "nosniff",

        "X-Frame-Options": "DENY",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "true",

        "Cache-Control": "no-store, no-cache",

        "Date": "Tue, 16 Mar 2021 12:34:10 GMT",

        "Content-Length": "724",

        "Content-Type": "application/json",

        "Expires": "-1"

    },

    "body": {

        "error": {

            "code": 504,

            "source": "flow-apim-europe-001-northeurope-01.azure-apim.net",

            "clientRequestId": "5e3224f7-d6f7-44f6-9d42-2d231556899c",

            "message": "BadGateway",

            "innerError": {

                "status": 504,

                "message": "Request to Graph API has timed out.\r\nclientRequestId: 5e3224f7-d6f7-44f6-9d42-2d231556899c\r\nserviceRequestId: 7b1420e0-cc66-4735-ada4-b13e9e002ed5;964a6534-6530-45a4-b0c5-aedba347c019;aaf5f5f0-23d1-4018-8006-ae3a825dde8b;e5254fa9-62ee-415d-bcc2-de769d3ce467;87d02b6b-d4d7-4a77-b1a2-c0594279495a",

                "error": {

                    "message": "Request to Graph API has timed out."

                },

                "source": "excelonline-ne.azconn-ne.p.azurewebsites.net"

            }

        }

    }

}

[annajhaveri]

@MoBrien excel file the flow is using, has there been any changes to the excel file since the flow has started to fail?

[MoBrien]

No changes,

The form responses are mapped to columns and a new row is created for each new form submission. 

At the moment, a new blank row is being created at the bottom of the table.

I have tried removing the blank lines and resizing the table to only include fully completed rows.

Regards

Matthew

[MoBrien]

@annajhaveri 

No changes,

The form responses are mapped to columns and a new row is created for each new form submission. 

At the moment, a new blank row is being created at the bottom of the table.

I have tried removing the blank lines and resizing the table to only include fully completed rows.

Regards

Matthew

[Andy_L]

Hi Matthew, did you find a solution to this please?

I have exactly the same problem 😞 

[annajhaveri]

@Andy_L  what is the size of your excel file?

[Andy_L]

Hi @annajhaveri and thanks for your response.
My Excel file is just over 7MB.
But I could archive some table rows if you think it would help, and slim down to maybe 2MB.
If file size is an issue, does Microsoft recommend any approach for regularly archiving data from such tables, so we don't run into this problem regularly?
Thanks

Andy 🙂 

[annajhaveri]

@Andy_L  yea try using 2 MB file or a different file just to see if it has issue with specific file or not

[Andy_L]

Thanks @annajhaveri , yes, that fixed it so confirming that my spreadsheet had gotten too slow to allow the 'add row' to complete without timing out. So I have removed most of the historic data and that gets the power automate job working again.

So now I need to tackle the problem of stopping this from happening again in about 6 months time. Can you tell me do you know of any good examples of a scheduled power-automate job - perhaps monthly - that I could reuse to do the following;

- process a table looking for records over a certain age (e.g. timestamp >6 weeks old)

- copy a subset of the fields to my archive table in another sheet

- then delete the records from the production table

Thanks,

Andy 🙂