Unanswered

Move File connector just stopped working when target SharePoint library hit 117,273 items.

(0) Share

Report

Posted on by Ellya

Hi,

To keep an active document library in SharePoint Online performing well for users, I've added an Archive flow to move docs out if they are older than 30 days. I use the Move File connector (with rename if exists) to move docs to an identically structured library in the same site. It's been working well almost a year now, but a few weeks back I spotted it just stopped working with the following error:

{"status": 400, "message": "Microsoft.SharePoint.SPException: A file with the name /sites/xxxxxxxxxxx/liberty16.xlsx already exists.

Given I expect items to already exist, the rename should handle that.

For testing, tried renaming the liberty16.xlsx doc and running the flow again, but it just failed on the next doc it was processing with the same 'already exists' error.

I created a new empty archive library and pointed the flow there and it works fine.

The failing library has 117,273 documents in it and all the columns in views are indexed.

Does anyone know why the flow should just stop at this number of docs in the target library?

Cheers, Ellya

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

v-xiaochen-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Ellya ,

I guess this is caused by too many files in your target library.

Although the file "liberty16" exists in the target library, it cannot be detected by 'move file' action.

So the flow performs a 'move' operation and reports an error.

Could you check this?

Best Regards,

Wearsky

Was this reply helpful? Yes No
Ellya 29 on at

Like (0)

Report
Copy link

Link copied!

Hi, I managed to do a workaround by creating a new Archive 2 library and pointed the flow to it. No other changes.
It worked for a few days and now has the same issue as before, only this time the Archive 2 library only has 12,792 items in it, and fails on many other files, reporting they already exist and won't rename the files being moved. Given all the columns are indexed and SharePoint should support 30,000,000 documents in a single library, I'm struggling to see why this is failing.

Was this reply helpful? Yes No
Ellya 29 on at

Like (0)

Report
Copy link

Link copied!

Just an update for anyone else hitting this issue. I've now switch the concurrency option on the flow to 1 and this seems to be hold out ok. No issues, since I cleared the last batch of errored docs.

Was this reply helpful? Yes No