SharePoint Copy File error

[tsyrell]

I have a fairly straight forward archive workflow to move older SharePoint library entries from a work library to an archive library.  The basic flow is as follows: Get Files (properties only) ->checks conditions -> if met then Copy File -> Update File Properties -> Delete File.  The conditions check for specific file types and last modified greater than 6 months. 

Right now I have it running daily, and every day I get multiple files failing with an error code of 400 an a msg saying "Source object has changed during copy process. please rerun copy operation to get the latest copy."  The next day when the archive job runs, the files that errored out, get archived.  

I would like to improve the efficiency of my flow.  For example, in the 3 runs this week, I had 22 files fail archiving with the error, only 3 archived on the first attempt, and 20 of the failed files archived on the following day.  The remaining 2 are failures today and I expect will archive tomorrow.

Is anyone else seeing this, or does anyone have any ideas on how to resolve the problem beyond just having them get picked up in the next cycle?  

Thanks,

Tom 

[SCTdan]

What if you compare the results of Get Properties when a file fails vs when it succeeds, perhaps a clue in there?

[tsyrell]

I will give that a shot.  I would assume, maybe incorrectly, that if anything changed, it would result in the 'last modified date' to be updated, but that's not happening.

[SCTdan]

I'm not sure what the resulting behavior would/should be, but is it possible that someone has the file open for viewing?  

[tsyrell]

I think that's extremely unlikely for these types of files as they are essentially old production batch files that are only kept for auditing purposes.  I could maybe see an occasional fail, but this is consistently failing more times than it initially succeeds in any run, and then next run always resolves the previous runs failures. 

I'll let you know if anything turns up with the properties.

[SaschaTorkel]

@tsyrell Did you figure out what the problem was? I am hitting the same issue and I'm definitely not touching the documents while the flow runs.

[MattWeston365]

Hi @SaschaTorkel can you please share a screenshot of your Flow? Also if possible, share the output of a failed file and a successful file. In the meantime I will try to build a similar Flow to see if I can recreate the issue.

[SaschaTorkel]

Sure:

@MattWeston365  I'm not sure what you exactly mean by "output of a failed and succesful file". Here a screenshot of one failed copy action:

The full error message:

{

"status": 400,

"message": "Source object has changed during copy process. please rerun copy operation to get the latest copy. Source file length 73655, target file length 75778, source file eTag \"{7635DB32-218D-4A35-A7DE-3D11EBEFB7A6},9\", target file eTag \"{7635DB32-218D-4A35-A7DE-3D11EBEFB7A6},8\" CallStack -- \r\nclientRequestId: 63ee2bf3-fa0d-4107-ad62-7ca70d69f0e1\r\nserviceRequestId: 63ee2bf3-fa0d-4107-ad62-7ca70d69f0e1"

}

As a workaround I put in the same copy action again set to "run after failed". For now all files get copied at least with the second try, but this is not a solution I like to put in production.

[tsyrell]

Hi Sasha and Matt

I never determined the isues, so I essentially ended up doing nothing.  When tracking the failed files, it appeard that when the flow ran the next time (it's scheduled to run daily), it usually picked them up.  Sometimes it took a secnd run, but they were always processed successfully.

[MattWeston365]

Hi @tsyrell and @SaschaTorkel 

I've been trying to replicate the issue. Never have I wanted my Flow to fail so badly so that I can try to help, but every test so far has been successful. Here is what my Flow looks like:

It's simple, but it seems to work every time (even trying with an old .XLT file format). In your Flows, what actions are taking place before you start the copy process?

[SaschaTorkel]

@MattWeston365 thank you for trying to reproduce this error. If you search for the exact error message, you get one hit on google: this thread. So this problem seems to be not that common.

Anyway, the flow is based on "new item created" trigger on a SharePoint list, where a user selects the documents to be copied via a PowerApps form.

Here are the immediate actions before the "copy document loop": https://1drv.ms/u/s!AtXsM1f8HFVSuAaSdm7VtqF3aRbB (Somehow i cannot embed images anymore here)

I prepare the loan ID, which serves als target folder name, which is set up by the create file action. Also I put the IDs of the documents, that should be copied, in to an array and use it in the apply to each loop.

[MattWeston365]

Thanks for that @SaschaTorkel , I'll refactor my Flow. I might also suggest an alternative method for copying/moving the file which might be worth trying.

On an aside, I found the same that this thread was the only one in search engines when searching for the error. On the bright side, you're top of Google 🙂

[giovani_martini]

Same problem here 

Im my case, flow is trigered by http call and allways fails in the first run .. same error.

[MattWeston365]

Hi @giovani_martini did you say that you were using the Send HTTP Request to SharePoint action and you're getting the same error?

[giovani_martini]

Hi @MattWeston365 

No, I meant to say that my flow trigger is "When an HTTP request is received". But that has nothing to do with the error on the action that copies the file to another library.

The error i am facing is the same as @tsyrell , "Source object has changed during copy process. Please rerun copy operation to get the latest copy."

I have this flow that is triggered manually by a http request, it should copy a document from one library to another using this action, simple as that!

Sometimes works, sometimes don't, and i don't know why, this error message is not helping.

[Anonymous]

I'm having the same problem.

The flow is triggered by flaging an email.

The flow copies 2 Excel files from one folder in a SharePoint library to another folder in the same SharePoint library.

The first file always copies and the second file sometimes fails.

Neither of the source files are being edited by anyone.

This is the error details reported by MS Flow:

Source object has changed during copy process. please rerun copy operation to get the latest copy. Source file length 241542, target file length 246391, source file eTag "{47C123A7-BC4C-432F-A23B-D77EF1AB98C7},99", target file eTag "{47C123A7-BC4C-432F-A23B-D77EF1AB98C7},98" CallStack --
clientRequestId: b0901234-567a-1b2c-d3e4-0a2b3c45d033
serviceRequestId: b0901234-567a-1b2c-d3e4-0a2b3c45d033

[giovani_martini]

Hi!

Looks like the error stopped, at least for me.

My flow did run 25 times without any error, and i didnt change nothing.

[AlexDorfmayr]

Hi everyone,

on our side this errors did just start like 1 week ago - same as above mentioned:

Source object has changed during copy process. please rerun copy operation to get the latest copy. 
Source file length 69829, target file length 72478, source file eTag "{3CA4FAE5-6B62-4D12-9C87-2DF7CA899EF9},5", 
target file eTag "{3CA4FAE5-6B62-4D12-9C87-2DF7CA899EF9},4" CallStack -- 
clientRequestId: 2e6ff3da-03ce-4f00-84d5-e6d1b5dd5c54
serviceRequestId: 2e6ff3da-03ce-4f00-84d5-e6d1b5dd5c54

I didn't do that much as just this actions happen bevor the crash:


Any help or evenguesses where to start fixing this could be helpful.

As the pre-comments already mentioned: without any changes the flow runs just smooth when you simply rerun it - so the same file, the same source, the same everything - just when you run it a second time everything is fine. At the first try it isn't..... and even that: sometimes the flow runs even at the first attempt.?!? 

[giovani_martini]

Hi @AlexDorfmayr 

I did some attempts trying to figure out why this was breaking. When the error was occurring to me, I have notice that the error happen mostly when the file was recently created or modified, or when file was opened while de flow runs.

But like I mentioned, this error stop for me. Hope you find a solution for you.

Best!

[Anonymous]

Hello everyone !

As mentioned several times above, I am getting the exact same error as you on a Flow launched by users on SitePages.

Here is the full error :

{

"status": 400,

"message": "Source object has changed during copy process. please rerun copy operation to get the latest copy. Source file length 21851, target file length 23881, source file eTag \"{C42CA771-AA8A-4F1F-B7A0-989DE2FA163F},16\", target file eTag \"{C42CA771-AA8A-4F1F-B7A0-989DE2FA163F},11\" CallStack -- \r\nclientRequestId: 601fb208-9d87-4c2c-89fc-1edfe9589dd2\r\nserviceRequestId: 601fb208-9d87-4c2c-89fc-1edfe9589dd2"

}

As you can see, the length and eTag are different. I don't know why it is happening right now, but it is a bit of a embarrassment.

I tried the solution of putting a second Copy action if the first fails, but this one does not work at all and get the same error as the first.

I tried re-running the flow several minutes later, after having the page created, but nothing changed either.

I have to precise : my flow is launched by the user on the SitePage library, on a single item, then several actions are processed, like setting variables, and checking if the file already exists. Then the Copy action that fails.

@giovani_martini, @MattWeston365 , do you have any idea, or is it just some SharePoint Voodoo ?