I have a flow built which runs a series of ExcelScripts. It has been running fine for the past 4-5 weeks.
Initially, when i went to re-read the ExcelScript - It decided that "ExcelScript" wasn't a valid namespace? Even though my usage of it is a direct copy of the examples provided. This caused around 2-3 Hours of unnecessary debugging, afterwards simply selecting everything - Cut'ing - then Paste'ing - And a final re-save of the script sorted that out. However...
Today it failed, and it failed on a step that is unchanged in the script;
We were unable to run the script. Please try again.
Runtime error: Line 4: Cannot read property 'getUsedRange' of undefined
The line in question is here from the ExcelScript in question;
Small Update (still unresolved)
Curiously around an hour or so after posting this, the flow decided to trigger itself 6 times over the course of 2 hours. This is a flow triggered by a specific email subject and I did not receive additional emails to trigger this. Of those 6 triggers, 1 of them managed to succeed.... With no changes to the script or context outlined above. The 1 successful trigger was the 4th one, with 2 following runs failing for the same reasons outlined above.
Sorry bud! We got a third party to develop us a solution outside of this issue avoiding the MS Platform entirely. Impossible to get any support so i would suggest trying to find options outside of the platform.
Capturing the Excel file locally as CSV and using something like https://docs.python.org/3/library/csv.html To parse and progress your automation.