Excel Online (Business) - Run Script Error - Graph Item not found, was it unshared or deleted?

[Anonymous]

I currently have a flow which:

- Receives email. 

- Saves attachment to SharePoint as .xlsx.

- Runs an excel script to convert the XLSX range to a table.

This works fine up to the execution of the script where I receive the error message:

"Graph Item not found, was it unshared or deleted?\r\nclientRequestId: ab7d8b91-be2c-4e96-973c-e7c7ffadaf37"

Manually opening the .xlsx file within Sharepoint and executing the script works with no issues.

Is anyone able to assist with troubleshooting?

[tommyvan]

I am also having this problem exactly.

[nicky9876]

Hi, I am having the same issue for 

Excel Online (Business) - Run Script Error - Graph Item not found, was it unshared or deleted?

Is anyone able to figure it out?

[Marcel_Wolf]

I am having also the same issue.  It occured since last week and the special thing is that if you Google for 'Graph Item not found, was it unshared or deleted?' there are only a few messages from 23 april till now.
i hope it gets solved soon.

[TomDenoo]

Same issue here as well. 'Graph Item not found, was it unshared or deleted?'

Hoping for a quick fix...

[Corbitbeeler]

I've been getting the same error. I have one main account and one service account both have same level of access and have their own one drive. I created the same instant flow and office scripts to the new service account (The flow i have made for my main account still works, but when I try to make the same one for this service account it doesn't work at all). Give them the same settings with small tweaks such as locations to copy too that is about it. Same process two different issues. Not sure why or what is different about them I hope for some answers soon on this or atleast a work around because my main account one works but I need a service account one for other user to run it.

[KuroWani]

I was getting this error too. I remade my scripts, saved them in the same folder as the Excel template sheet I use and remade all script parts in my flow, now it's working perfectly again. I don't know specifically which of these actions fixed it though.  

[MattLincoln]

I too am also having this issue, with nothing relevant showing up when searching the error message. Any news on a fix at all?

Edit: 

I'm not sure if this will help anyone, but the issue was resolved when I concated the folder path from OneDrive (eg. /Folder1/SubFolder2) with the file name that I had saved in a variable earlier in the flow to make a full file path in the 'File' field of the  Run Script:

When using just the file name or pulling through the Path element the pa flow couldn't find the script.

[Marcel_Wolf]

This is also the solution for me.

[Anonymous]

I am getting the same error.

We are running a daily PA script that iterates over 16k records on an Excel sheet, breaks them down into data arrays based on supervisor, then creates individual excel sheets per supervisor and emails them out.  What's weird is that out of 380 data sets, the error only happens on 1 data set - which was the same data set each time.

Some details in case it helps with troubleshooting, our flow runs an Excel script to check which emails need to be sent out on a given day (based on which supervisors have employees with items past due, which day of the week it is, etc).  On Friday, the report only sends out to those with employees past due.  The flow ran successfully for all but one record set, we will call it record set X.  On Monday the emails send out to all record sets, regardless if there are past due items, and the flow ran successfully.  No errors on any record set.  On Tuesday the flow again only sends reports to supervisors with employees past due.  Again, record set X was the only fail.

Record set X appears to be no different than any of the other record sets.  Roughly the same quantity / quality of data.  I have checked the record sets that are running right before the failed set in case they are actually the issue, and again - nothing out of the ordinary.

Our script, and the Excel file, are both stored in Sharepoint.  The path to the file is dynamic, based on the path passed from a previous "create file" command.  (There is no concatenation as brought up as a possible solution since the path is simply the path output from the "create file" command.) The template file created properly each time, it was during the script where the data itself is populated on to the sheet that I get the "Graph Item not found, was it unshared or deleted?" error.

[stevhsu]

Thank you Matt. 

How I solve the issue is using your suggestion with string function concat. So, this error message means the run script cannot find the file in the sharepoint.

Spoiler

concat('/Shared Documents/General/Documents/xxxxxx/xxxxxxx/',outputs('Create_file_2')?['body/Name'])

[Corbitbeeler]

For a heads up with people if you wish to try and use a Script from a Sharepoint site it looks to be available now. You can now run scripts directly from Sharepoint sites which has worked greatly for me.

[Anonymous]

I too have same error

[davidparsons]

This can be caused if the location you are referencing has more than 100 items within the folder. I resolved by creating a new folder within the library and moving the script to there then running it within my power flow. 

[Munyiva]

I got the file properties then used the Full Path output to ran my script.

[GetsugaTenshou]

Hello Matt,

Please share some guidance on how I get the file name to concatenate, the file name that I get when I view the file on OneDrive online vs when using OneDrive via my file explorer window, differs and I can't seem to get it to work. 

[PaulMc1]

This worked perfectly for me. Thank you for posting!

[waytu]

I ran into this issue and it took a few hours to determine the cause. In my case I was copying an Excel workbook in SharePoint online and then completing processing on that copied file, importing data from it and then deleting it. I determined the cause to be that I had browsed to a copy of that temporary file and selected it within my Flow steps and then saved the Flow. As far I can determine when you do that what is actually saved is the SharePoint DocumentId. Because my Flow created and deleted the file that DocumentId changed every time it ran so it could not find the Workbook. I fixed it by initialising a string variable and storing the document location within it, I guess, forcing it to parse at runtime as opposed to save time. I guess that is how MattLincoln solution works too.

[Dazza_Aus]

Hi everyone,

I just re "addressed" the file location and this fixed the flow. (once anyway!!!)

Will test again tomorrow!

cheers

[RP5]

Can you share what this looked like?

I'm having the same issue-

Converted MS form response to a multi-sheet workbook.  Save it under a new name, run a script to delete the un-needed input sheets, and email the complete sheet back out.

It worked fine up until last Fri, now the run script flow step fails even though the script itself runs fine in a web browser.