The resource you are looking for has been removed

[Cheney]

My flows were heavily connected to O365 Sharepoint list and it worked until 3 days ago.

it's scanning every list items in the sharepoint (with apply to each loop) and do some actions to microsoft planner then update the selected list item.

Now, some of the items in the sharepoint shows 404 error, The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. When i checked in the sharepoint, the items should be there.

Has anyone know how to solve this error?

This image shows only error on item 7 of all 12 items

[v-micsh-msft]

Hi @Cheney,

Do you have any actions or condition that would delete the item?

If there is a delete action before the Update item, then it will show the item deleted information.

Besides, have you checked the SharePoint list, are all the items still there?

Regards,

Michael

[Cheney]

The flow only consists of create item and update item. It has no delete action.

I'm trying to delete and re-insert the action with no luck. The error is still there 😞

Weird things I found:

My flow runs on daily recurrence basis. Let's say the flow need to update 12 items in the sharepoint list. On 1 day, it showed error when it was updating on item 4 (with ID 39) of 12 items. On the next day, it showed error when it was updating on item 1 (with ID 4) of 12 items but, updated item 4 (with ID 39) successfully. The items are still available in the list and not deleted. I can access them with REST API manually.

Is it possible that the type of data that the flow tried to input to the sharepoint list may be mismatch? How could I check it?

[v-micsh-msft]

Hi @Cheney,

I agree.

The Apply to each works for the items returned by the previous steps, a collection called Value as the input, the first thing that should check is the Item Id field, please ensure that the Id is properly matched.

The Id should come from the SharePoint Get Items Action, 

Another thing is the situation I mentioned in my earlier posts, make sure there is no delete action when flow runs.

See if this would make any difference.

Regards,

Michael

[Cheney]

Thanks for the reply Michael.

I've already done that in my flow. I've used the provided dynamic contents and it showed the error I've described.

[Cheney · Accepted solution]

Just want to make a response here.

The issue has been resolved by itselves starting Sept 1, 2017 😐