Thanks for the reply again. This XML from my file has all these custom override as in your screenshot.. Also tried to copy paste the same content to a new Excel worksheet, and it doesn't fix the custom entries in content type xml in my end.
I have been utilizing this Run Script step in my Power Automate flows and it has been working great for months. Today they all failed. Can't figure out why they are all of a sudden failing.
Hi @pb1051 ,
I have made some adjustments to the flow as suggested by others, and it has been working fine so far. I have added "Get file Metadata" in the flow. You might consider replicating the same approach. My flow is as follows:
@Olze-Kay
start with Excel and go to the Automate tab and click on ‘New Script’
In the editor that will pop up on the left, delete everything and replace it with,
function main(workbook: ExcelScript.Workbook) {}then save the script with a name of your choice, the script will save in your office scripts folder of your OneDrive
In your power automate flow, add a new activity, Excel Online (Business) Run script after your create file action which is likely a SharePoint or OneDrive create file action.
Fill in the four fields for the Runs script action as,
Location: the location where you created the file, choose OneDrive for business if you created the file on your one drive, else the sharepoint location you created it.
Document Library: should be Documents
File: use dynamic content and add body/Id when you over it should show something like the below, assuming your previous create file action is labelled Create file,
outputs('Create_file')?['body/Id']
Script: you should find the script you just created in here, select that one.
That is it.. good luck..
Hi @90_eryka
assuming your saving action is storing an exact copy of the attachment, that copy will still have the custom overide entries in the xml. at this point if you open it and save it the power query connector will read it ok. This is where the run script action automates that for you.
your flow should look something like the below, the for each loop will iterate through all the emails attachments.
Confirm that what the flow saves in your sharepoint is actualy what you are expecting, the xlsx file.
Your condition logic should only select the attachment you are after, you can add something like, item()?['name'] ends with .xlsx or use the exact name of the attachment to be more precise.
If there are images like logo's ect in the signature, these are also attachments, make sure you are not picking those up and storing them. For example if the body of the email had 2 images in the signature and one excel attachment, without the logic your create item will save each one with the same name in the same location so only the last one will exist which could actually be an image which is causing your problem.
Hi @fr_jc ,
I’ve confirmed that there is no extra image, and I’m storing the exact file as per the attachment.
I’ve also added the condition you suggested, along with an additional step to delay the flow by 5 seconds (as recommended by Co-pilot) to ensure the file is fully created before the script runs. However, the Run Script step still fails. Is there any step I might be missing?
Thank you.
@90_eryka that looks to be right from what I can see with actions.
can you maybe share the actual error description that you are getting?
Just checking on the Run Script actions location and doc library.
The location should be the same site you used in the previous create file action
if you look at the code view you should see the source name for the run script should match the dataset name of the create file.
The Document library normaly defaults to Documents, I see you have Analytics. Did you slect this from the availble drop down or did you add as a custom value?
Hi @fr_jc ,
The error message is "Flow run failed". My script in excel is
Also I did select "Documents" for Document Library but the flow still failed
That all looks ok to me, but let’s go through it again.
The delay action is good if the file is slow to create or is stuck in a locked status. Normally though you would receive a file is locked error,
Using a Do Until action can work well here if the file is locked.
The office script is correct; you do have a space between the curly braces but that shouldn’t make any difference. You should be able to test it by simply running it in excel and it should look like it does nothing, but it should run successfuly without error.
function main(workbook: ExcelScript.Workbook) {}
Your Create File action is storing the attachment in a SharePoint location using the same name as the attachment.
Your Run Script action is,
- correctly using the same SharePoint used in the created file location as its Location source.
- You have selected the default Document Library ‘Documents’
- You are correctly using dynamic content using the path from the Create File for the File
- The Script you have selected I have to assume is ‘function main(workbook: ExcelScript.Workbook) {}’ saved as CleanAndResaveExcel
For the error, we should see a more descriptive error other than “Flow run failed”. We need to pin point where it fails.
Are you able to share a screenshot of where in the flow the red x’s appear? On that action it should show the error that we are interested in.
Does the run script have any output log or does it fail before generating one?
@pb1051 You need to use "Indentifier" instead of "ID". And I also recommend to create the condition only for creation (not modification of the file). As the condition formula you can use timestamps Modified=Created. Otherwise the file will be touched twice: first time when file is uploaded to the folder and again when the flow modifies it.
Helpful resources
Power BI Monthly Update - November 2025
Check out the November 2025 Power BI update to learn about new features.
Fabric Data Days
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
FabCon Atlanta 2026
Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
