Office Scripts Down? Run a script in excel 403 and 502 errors

(1) Share

Report

Posted on by majorfriend

170

"Anyone else seeing errors when running a script in Excel?

We're getting 403 errors "The server experienced an issue and couldn't run the script. Please try again in a few moments"

I get the same message but with an error code of 502 on the run script step when trying to edit the flow.

This connector use to regularly have issues - but it's been quite a while, guessing something is up server side, but wanted to see if anyone else was getting the same.

Categories:

General topics

I have the same question (11)

All responses (6)

Answers (0)

Suggested answer

Tomac 3,966 Moderator on at

Like (0)

Report

There's no issues currently showing on the Fabric platform, but you can use that link to submit a ticket to Microsoft to notify them of an emerging issue.

Was this reply helpful? Yes No
majorfriend 170 on at

Like (0)

Report

I don't think Office Scripts are Fabric related are they?

Was this reply helpful? Yes No
Tomac 3,966 Moderator on at

Like (1)

Report

I would start there and let them point you to another resource. Scripts running in the Azure Cloud are likely part of Fabric.

Was this reply helpful? Yes No
Zebaronlau1 2 on at

Like (0)

Report

I'm also having the same issue, from within excel desktop/web, and also from within powerautomate. I've opened a ticket with microsoft, I suggest you do the same. Also confirm with your IT this service is not disabled in office 365 admin.

Was this reply helpful? Yes No
Suggested answer

MK-14081725-0 4 on at

Like (0)

Report
Hi everyone, I’m facing a similar issue and wanted to check if others are experiencing the same.

In my case, we have a Power Apps application that calls a flow to import data from Excel. It was working fine, but since yesterday we started getting the following error:

ImportarExcel.Run failed: { "error": { "code": 502, "source": "msmanaged-na.azure-apim.net", "message": "BadGateway", "innerError": { "error": { "code": "NoResponse", "message": "The server did not receive a response from an upstream server." } } } }

In other words, the connector is not getting a response from the server. The failure happens right on the step that runs the script in Excel, which looks very similar to the 403/502 reports mentioned here.

We’ve already checked permissions and connections, but nothing changed on our side — which makes me believe this could be some intermittent issue with Microsoft’s service (Office Scripts/Excel Online).

Is anyone else seeing the same symptoms? Has Microsoft confirmed any outage or instability with the Excel/Office Scripts connector?

And if anyone has found a workaround to temporarily get past this issue, could you please share it here?

Thanks in advance!

Was this reply helpful? Yes No
JV-02100952-0 2 on at

Like (0)

Report

Hi All,

I’m reaching out for urgent assistance. We have a Power Automate flow that has been running smoothly for nearly two months, but it suddenly started failing yesterday when executing the “Run Script” action for Excel Online. This issue is affecting all our flows that use this function, and we haven’t made any changes to the scripts or flow logic. It was working perfectly just two days ago, and now we’re consistently getting errors — including 429 (Too Many Requests) and internal server errors from Azure Resource Manager. If anyone has encountered this or knows what might be causing it, I’d really appreciate your help. We need to get this resolved as soon as possible.

Thanks in advance!

Was this reply helpful? Yes No