Sharepoint Action Copy file Error

(1) Share

Report

Posted on by garvoberoi1999

Hey,

In one of my power automate flows I am using the 'copy file' sharepoint action to move my file from one sharepoint library to another, which are both under the same site.

The trigger is , on create a file in Library A. Although the file size tends to be more than 100 Mbs, it never used to be a issue and never used to throw an error.

Recently have noticed that it started throwing error: "'file A' cannot be copied or moved because of error code '-2147213162'. clientRequestId: X serviceRequestId: Y".

The error is not descriptive enough to tell me what the problem is, Please let me know if any of you have received the same error in the past and found a solution.

Thanks,

Categories:

Building flows

I have the same question (2)

All responses (4)

Answers (0)

Expiscornovus 33,828 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I haven't seen that specific error before.

However, that Copy File action should do the same as the Copy To command/button in the SharePoint library.

https://learn.microsoft.com/en-us/connectors/sharepointonline/#copy-file

Have you tried copying that specific file in the interface as well? Maybe that gives you a clue (a more specific error) why it is not working.

Was this reply helpful? Yes No
ShantanuSri 21 on at

Like (0)

Report
Copy link

Link copied!

@garvoberoi1999 Were you able to resolve this. I am getting the same error.

Was this reply helpful? Yes No
JW-29091351-0 2 on at

Like (0)

Report
Copy link

Link copied!

I had the same error and not all file sizes were bigger than 100 Mbs.
When i submitted the flow again, it worked fine again, so i don´t understand what caused this error.

Also the copy to by command button of the interface worked well.

Was this reply helpful? Yes No
Suggested answer

ProPosia 58 on at

Like (0)

Report
Copy link

Link copied!

The SharePoint “Copy file” action has been flaky lately on big files and certain libraries. The most reliable fix is to stop using the “Copy file” action and switch to the SharePoint CreateCopyJobs API via “Send an HTTP request to SharePoint.” It’s the same engine behind SharePoint’s modern Move to/Copy to, handles large files, and avoids the recent connector regressions. Proof + steps below.

Why this works (with proof)
{https://learn.microsoft.com/en-us/sharepoint/dev/apis/spod-copy-move-api
https://reshmeeauckloo.com/posts/powerautomate-movefile-bypassinglock/
https://learn.microsoft.com/en-us/answers/questions/5344705/power-automate-copy-file-no-longer-works-copy-shar}
CreateCopyJobs is Microsoft’s supported API for copy/move jobs in SharePoint/OneDrive/Teams and is what the UI uses under the hood. It’s built for large files and cross-library/site operations.
Community implementations show CreateCopyJobs succeeding where Copy file fails, incl. moving past “locked” issues and copying full version history.

There were recent breaks in the Copy file action (“invalid number value”, sudden failures). Switching to CreateCopyJobs bypasses the connector bug.

Was this reply helpful? Yes No