Power Automate Excel Script - Run from sharepoint is SLOW

(0) Share

Report

Posted on by CY-21010957-0

So, i'm running into an issue with a flow I built which was working fine & it will run, but not complete one of the excel scripts from sharepoint.

I have checked & we haven't changed any of the connection references, the script, the script's location or the location of the excel file it is looking up against.

I tried running the script manually and it works in around 15s, so don't think it's an issue with the script itself.

To add confusion, I have a parallel script doing the exact same thing (albeit with a few thousand less rows) that runs absolutely fine and takes 8sec to run. Previously this problem script would take 36 seconds to run, but now wont run even if I leave it for 15min.

Has anyone got any ideas as to why one script would run & the other wouldn't and what might've caused the script to suddenly break?

Categories:

Using flows

I have the same question (1)

All responses (2)

Answers (0)

Suggested answer

David_MA 12,966 Super User 2025 Season 2 on at

Like (0)

Report

You don't show your flow, so I don't know how the script is being used or how you have created the script or which Office Script action you are using to run it. However, if you created an *.osts file for the script, these should be saved to the OneDrive of the owner of the flow in the folder Documents > Office Scripts as noted in Office Scripts file storage and ownership - Office Scripts | Microsoft Learn.

If the script is being run on the account of the owner of the flow, I would move the file to this folder in the owner's OneDrive and run it from there to see if that improves performance.

Was this reply helpful? Yes No
nico32 2 on at

Like (0)

Report

For the past few months, I've observed the same thing: a script that used to take 30 seconds to run now takes 1 to 10 minutes! There's no difference whether the script is in the workbook, in the flow owner's OneDrive, or in SharePoint. When I run the script from the workbook, opened in Excel or in the browser, the execution time drops back down to 30 seconds. I think Microsoft is intentionally slowing down this kind of job.

Was this reply helpful? Yes No