Excel Run Script - 502 Bad Gateway

[MatthewLloyd]

Have a flow which sends an array of objects to be sorted by their date using an office script. Was working fine for months until two hours ago started recieving the below errors. We haven't any significant changes I'm aware of in the past two hours that may have caused this:

{

  "error": {

    "code": 502,

    "source": "australia-001.azure-apim.net",

    "clientRequestId": "xxxxxxx-xxxxxxx-xxxxxxx-xxxx-xxxxxxxxxxx",

    "message": "BadGateway",

    "innerError": {

      "message": "Failed to find certificate with subjects 'aadencrypt.officescripts.microsoftusercontent.com', 'aadencrypt.runtime.arbitraryrunner.com'\r\nclientRequestId: xxxxxxx-xxxxxxx-xxxxxxx-xxxx-xxxxxxxxxxx",

      "storageErrorCode": 0

    }

  }

}

[CaptaionPower]

I checked our flows and we are back in businness!

Thanks for the help and the info!

[Yutao]

@AlCow - Office Scripts is still a young service and we have been working with our partner teams to figure out the best communication channel for this kind of situation. I would also like to hear your opinions - where would you expect to see/receive/check the status of outages?

[jiwhite]

I would expect a link to a Power Automate Status page in the Support menu at the top of the page.

[AlCow]

Brilliant, all back up and running, thanks @Yutao!

I agree with @jiwhite, some sort of status page in the support menu would be really helpful

[Max_Power]

Dear @Yutao,
our flows are back, too. Thank you for your effort!! I also agree with @jiwhite.

Is it possible that you can give us an insight why this error may occurr, please?
As far as I know the 'BadGateway' has something to do with write protection, doesn't  it? But in my case I don't know why my template file, that my flow is using, should have a write protection for a specific amount of time? Back in time I also ensured that this file is not editable by any other person than me and then saved it again. After this adjustment everything was working well again, so I thought that this was the solution ...
Currently my colleagues and I were experiencing this issue two times in September. Due to this current issue frequency and because the flows are crucial to us and we do not know why the issue appears, I have added a kind of 'notifcation' to each flow that is containing the Run Script action to at least know if the issue has returned and to inform the user about the issue (see image below - hoping it is readable and may be helpful to you).











Thank you for your reply!

[AlCow]

Brilliant idea! I've just added that to my Flows. Thanks @Max_Power 

[donbui]

Any issues with North Europe again today? - We're getting a lot of 502 again, which makes this the 3 "big" outage" in september alone 😞 @Yutao 

[Snoemannen]

I'm wondering the same, I have a flow that is running an office script to do a regex search on a string and today randomly it started throwing an error saying "Unauthorized", I redid the script and getting the same error.
Got some unexpected error in excel online while doing it as well so it seems like there is someting wrong.

[Yutao]

Hello @donbui , @Snoemannen, thanks for reporting the issue! There was indeed an outage in the West Europe region and it got mitigated around 9 AM Pacific Time (5 PM West European Time?).

We believe this incident shared the same root cause of the last one in North Europe, but we are still working on to fully understand the problem and how we can better prevent/detect it in the future.

Really appreciate your patience and understanding!

[Yutao]

@Max_Power - thanks for sharing the notification flow, pretty cool and useful!

In most cases, the "Bad Gateway" errors are normally caused by things happening on the service side. There are  indeed some situations when issues in the script or the workbook themselves would cause such failures. We're in the process of identifying those issues and trying to add more helpful troubleshooting information in the output logs.

[Max_Power]

Thank you for this insight @Yutao!

Keep up the awesome work. I think we all know that issues are part of the game 😉
Good luck for the on going process

[Yutao]

Thank you so much for your support and understanding @Max_Power ! Office Scripts users are the best! This is what inspires me to enjoy my work everyday 😁!

[Ain]

Hi I also experience this problem - Malaysia

UploadExcelFile.Run failed: {
"error": {
"code": 502,
"source": "asia-001.azure-apim.net",
"clientRequestId": "649c45ca-69d6-44ca-994d-0e2a65da7843",
"message": "BadGateway",
"innerError": {
"error": {
"code": "NoResponse",
"message": "The server did not receive a response from an upstream server. Request tracking id '08585367985505604499081931420CU25'."
}
}
}
}

[Yutao]

Hi @Ain , can you please confirm this error was from the execution of the "Run script" action? I wasn't able to find any logs on our side for this particular request ID. Thank you!

[Anonymous]

Hello Yutao, i am getting the same issue now in Spain, my flow can´t access the API to get the tables

[Yutao]

Hello @Anonymous ,

Based on your screenshot, the issue seems to be in the "List rows present in a table" action, right?

My team only builds and supports Office Scripts (the "Run script" action) so I'm probably not the best person to assist you here. But if you are still seeing issues with the "List rows present a table" action, please let me know and I can try to find some folks from that team to help to take a look.

[Anonymous]

Thank you, i already found the problem, it was that the excel has the option approved or pending, and I think PA can´t access a pending file because it is saw as it being modified

[Wiesje13]

We have been facing issues with the Bad-Gateway all day. 

We only run the Office Script - Run Script.

Here are a few of our ClientIds:

71cf2a04-5dc2-41f0-8e80-c12427bb3e98

710ee543-71c4-437a-988e-4a5f099a6419

[Yutao]

Hello @Wiesje13,

The Run script action in Power Automate has a 120-second timeout limit (Platform limits and requirements with Office Scripts - Office Scripts | Microsoft Learn). Based on the logs of the two executions, it seems they each took more than 250 seconds. You can try taking a look at Improve the performance of your Office Scripts - Office Scripts | Microsoft Learn and see if you can optimize the performance.

BTW, are you seeing the timeout issue just recently? Did it work before? Were there any changes to the script or the workbook that might cause the execution to run longer? For example, did more data get added to the workbook?

[AlCow]

HI @Yutao 

We have some flows that have been running OK since last April. Now, they fail when they try to call the script. We can't even recreate a test version of the flow, because we can't even see the script listed when we try to setup "Run Script". All the scripts are shared, and we can see them when we look at the file itself. Any ideas?