504 Bad Gateway - Run Script Action

[BenMunk]

I'm building a new flow and getting 504 Bad Gateway trying to use a Run Script action.

In summary, the flow Gets Sharepoint List Items > saves as CSV > Run Script converts CSV to Excel.

It works occasionally if I only include 1 row of data from Sharepoint.  It has never worked if I include anything bigger.

(noting that 100 rows is about 70 KB - so it shouldn't be a size problem).

I'm expecting it might be a temporary MS issue ?

Here's the error output

{
    "statusCode": 504,
    "headers": {
        "Pragma": "no-cache",
        "x-ms-datasourceerror": "True",
        "x-ms-request-id": "d2beba36-f823-4af6-a0d8-c38f0f17df17",
        "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",
        "x-ms-apihub-obo": "false",
        "Cache-Control": "no-store, no-cache",
        "Date": "Wed, 01 Feb 2023 00:01:19 GMT",
        "Content-Length": "498",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "error": {
            "code": 504,
            "source": "australia-001.azure-apim.net",
            "clientRequestId": "d2beba36-f823-4af6-a0d8-c38f0f17df17",
            "message": "BadGateway",
            "innerError": {
                "status": 504,
                "message": "Request to Graph API has timed out.\r\nclientRequestId: d2beba36-f823-4af6-a0d8-c38f0f17df17",
                "error": {
                    "message": "Request to Graph API has timed out."
                },
                "source": "excelonline-ase.azconn-ase.p.azurewebsites.net"
            }
        }
    }
}

[v-dezhili-msft]

Hi @BenMunk ,

Could you please show me a screenshot of your flow?
What does your script look like?
You can try to use the template file in the link below, I did a test with it, and it works fine.

Convert CSV files to Excel workbooks - Office Scripts | Microsoft Learn

Best Regards,

Dezhi

[BenMunk]

Thanks for doing that test.  I originally followed the instructions in that link. 

I'll do a test with the template files as you suggest. 

This way, if it still fails I'll know that its a region MS problem.  ... Otherwise it must be a problem with my excel / csv files. 

Just strange that it would work sometimes and fail other times, with exactly the same sharepoint row of data.

I will report back.

[BenMunk]

There must be something corrupted in my flow. 

If I keep re-running it sometimes it succeeds, sometimes it doesn't.

If I run a simple flow using the CSV template from the MS Solution Link the Run Script action works fine.

Simple flow that works fine.

My flow that only works sometimes

[BenMunk]

Example of "sometimes it works"

[MichelleRanMSFT]

Hi @BenMunk, thanks for your question! It looks like the issue you're running into is that you're trying to process too much data in one go. You can try synchronizing/flushing data periodically as described in this sample: Convert CSV files to Excel workbooks - Office Scripts | Microsoft Learn

If your flow still ends up timing out, you might need to process your data in batches, like so: https://github.com/OfficeDev/office-scripts-docs/issues/470#issuecomment-1090657702 

Let us know if that helps!

[BenMunk]

@MichelleRanMSFT  thanks for your suggestion, but the test runs below only cover 1 row of data.  Although it is about 50 columns, I wouldn't think its a size problem. 

Since it works fine for me with the clean/simple excel templates in the example by Microsoft, my next theory is that something in the Sharepoint record (eg. special characters) might be causing the problem.

[Yutao]

Hi @BenMunk would you mind providing a new clientRequestId from a more recent failure like this from the Run script action? I was trying to troubleshoot using the clientRequestId from your original post but somehow it didn't return much useful information in our logs. Wondering a more recent one might help. Thanks!

You can find the clientRequestId from the Error Details pane of the run history: