Flow Failing 404 Item not found

[Anonymous]

Hi All, 

My Flow is randomly failing about 30% of the time 

It returns status 404 Item not found when trying to delete Items in a sharepoint list. First I get all items in a list, then I apply to each to delete them all. The delete step is the one that fails. Does anybody have any Idea what I can do to fix this?

{
  "message": "Item Not Found\r\nclientRequestId: 48850471-fa62-4f26-869a-7555ab8d6b95\r\nserviceRequestId: 2c22609e-403b-5000-b801-b867aff589b9;2c22609e-0044-5000-b801-bdd2c827fd59",
  "status": 404,
  "source": "https://testsiteblablabla.sharepoint.com/sites/test/_api/SP.APIHubConnector.DeleteListItem",
  "errors": [
    "-1",
    "Microsoft.SharePoint.SPConnectorException"
  ]
}

[v-xida-msft]

Hi @Anonymous,

The error message told that the item that you specified within the "Delete item" action could not be found within your SharePoint list.

I have made a test on my side and don't have the issue that you mentioned. My flow's configuration as below:

The flow works successfully as below:

Please check if you have filled proper Site Address and List Name within your "Delete item" action. In addition, please also check if you or someone else deleted some items within your SharePoint list when your flow is running.

You could also find the specific item that could not be found within your SharePoint list based on the error message, then search for your SharePoint list to check if the specific item is not existed in your SharePoint list.

Best regards,

Kris

[PAM-thrive]

I have to say that this was the worst reply/answer you could have supplied, that's like a developer saying "it worked in dev environment" when something fails in prod.

@Anonymous I am interesting if you found a solution to this. Sharepoint is such a flaky and rubbish piece of software and flow is such a delicate little flower that falls over in the smallest of winds, combing them both is a nightmare of problems.

I now have this same issue. I've had it before but it "just went away". But now I have it ongoing and do not understand why flow gets a list of items and then "one disappears' by the time it gets to the step of removing one of the 5000+ items it got a list for.

To be honest, it's embarrassing that you have to delete them one at a time. Well done microsoft! it's like 1990 all over again.

[srastogi]

I just realized that file names don't like special characters including the # sign. I have used replace function and that seems to have resolved some of my problems

[srastogi]

I just realized that file name doesn't like special characters including the # sign. I have used 'replace' function to look for special characters and remove them. That fixed many of my problems.

[Sagarchikhale7]

Hey can you share the updated flow with the replace function. Facing a similar issue

Would be great help, thanks.

[srastogi]

replace(replace(replace(replace(replace(replace(replace(triggerOutputs()?['body/subject'],'#',' '),'/',' '), '\', ' '), '@',' '), '<', ' '), '>', ' '), '%',' ')

[Sagarchikhale7]

Can you share the flow?

[srastogi]

Flow can't be shared due to proprietary information. Let me know if there is anything regarding your specific replacing file name query that wasn't answered in the syntax I gave earlier

[Sagarchikhale7]

Hey thanks for quick reoly, I just want to know where you added the replace function(after which step) and was it using the "Compose" action of logic apps? 

Context: 

I have a flow of moving files from blob storage to sharepoint, but some files have special characters in its name and hence giving 404 error while moving it. 

I am using a list blob trigger to get all the files from my blob location and then moving them to sharepoint. So where exactly should i use the replace function?

[srastogi]

In my flow, we were creating a PDF file from an email. During this creation process, we used the subject of the email as the file name (first 40 characters of it). Since we can't control what comes in the subject of an email, we did a replace of all special characters and then used the sanitized string without the special characters for creating the file.

So in case your process works fine during the file fetching, then my suggestion will be to get the file name, cleanse the file name and then save the file in sharepoint with the cleansed filename. 

[arkinex]

I know this a bit old, but I ran across the same issue and wanted to share the change in the step needed to get this to work properly.

I used the code from @srastogi to make this work (Thanx for that!!!!)

The pic on the left was the original and the pic on the right is the fixed view. The final Code is at the bottom.
Let me know if this does what you hope it does.

I just took the code from @srastogi  and replaced the:  triggerOutputs()?['body/subject']
from that code and replaced that with the code I got from my original piece which was this for me:  
items('Apply_to_each_3')?['DisplayName']

My final expression:   replace(replace(replace(replace(replace(replace(replace(items('Apply_to_each_3')?['DisplayName'],'#',' '),'/',' '), '\', ' '), '@',' '), '<', ' '), '>', ' '), '%',' ')