Moving a File Error Workaround

(2) Share

Report

Posted on by EC-14041929-0

I am trying to move a file from one document library (where the file was created from a form submission) to a folder in a different document library but keep getting an error that the file is too large (over 90MB), however my file is only 40MB.

The file from the form contains a .story file attachment. I tried zipping the attachment, and uploading a small PowerPoint file instead and still got the same error. Does anyone know why this is happening and is there a work around?

Categories:

Building flows

I have the same question (0)

All responses (13)

Answers (0)

Sort by

Suggested answer

Fredrik_A 3,644 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hey,

if possible, try using copy file and delete file instead, there are no size limits on those.

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @EC-14041929-0,

The "Move file" or "Copy file" actions in Power Automate have internal size limits (often around 50-100 MB). Even if your file is 40MB, the action might fail due to throttling or temporary service limits. Can you please do a cross check with file less than 30MB?

Reference: Handling Large Files in Power Automate - Manuel T Gomes

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Your file is NOT too large.

The flow is hitting an internal payload limit due to how the file is processed (Base64/memory).

Fix: Replace your logic with:

SharePoint “Move file” or “Copy file” action (no content handling)

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @EC-14041929-0,

The error is not about your actual file size. It's about how Power Automate handles files internally.

When Power Automate moves or copies a file using the "Get file content" + "Create file" pattern, it encodes the file as Base64 to pass it between actions. Base64 encoding adds roughly 30% overhead. So your 40MB file becomes around 52MB inside the flow, and depending on what else is in the payload, it can push past the internal message limit that triggers that 90MB+ error.

The fix is to stop routing the file content through Power Automate entirely and use the SharePoint Copy file action instead.

Copy file works by telling SharePoint's backend where the source file is and where to put it. The file never actually passes through Power Automate's message pipeline so the size limit does not apply.

Here is the pattern:

1. Trigger: When an item is created (your existing trigger)
2. Action: Copy file (SharePoint connector)
- Current Site Address: your source library site
- File to Copy: the file identifier from the trigger
- Destination Site Address: your target library site
- Destination Folder: the folder path in the target library
3. If you need to delete the original after copying to simulate a move: add Delete file after a successful copy

This avoids the Base64 encoding problem completely and works well for files up to SharePoint's own limits.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
EC-14041929-0 26 on at

Like
a
(1)

Report
Copy link

Link copied!

@Valantis I am using the sharepoint connector to copy the file, but still getting the error.

Was this reply helpful? Yes No
Fredrik_A 3,644 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hey,

Weird that you still get size errors when trying to copy. You could try using the api instead via an HTTP call to SharePoint as below, not sure if it makes a difference in this case, but worth a shot.

POST

_api/SP.MoveCopyUtil.CopyFileByPath()

Body:

{ "srcPath": { "DecodedUrl": "https://sharepoint.com/Documents/FILE.docx" }, "destPath": { "DecodedUrl": "https://sharepoint.com" }, "overwrite": true, "options": { "KeepBoth": false, "ResetAuthorAndCreatedOnCopy": false, "ShouldBypassSharedLocks": true } }

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
EC-14041929-0 26 on at

Like
a
(1)

Report
Copy link

Link copied!

I am a curriculum designer flying by the seat of my pants....lol...I don't know how to do anything with code.

Where would I put this?

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @EC-14041929-0,

No code needed, the fix is just changing one field in what you already have.

Looking at your screenshot, the problem is in the Copy file action. In the "File to Copy" field you have "File Content" mapped in. That is what is causing the size error File Content is the actual encoded data of the file, which is exactly what we are trying to avoid passing through the flow.

The Copy file action does not need the file content. It just needs to know where the file is. So:

1. Open the Copy file action
2. In the "File to Copy" field, remove "File Content"
3. Instead, use the file identifier or file path from your trigger — in the dynamic content picker from your trigger, look for something called "Identifier", "File path", or "Name" not File Content

That tells SharePoint where to find the file, and SharePoint handles the copy on its own without the file data ever passing through Power Automate. That is what avoids the size limit.

If you are not sure which field to pick, open the dynamic content panel when your cursor is in the File to Copy field and look for the option that shows the file path rather than the file data.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
EC-14041929-0 26 on at

Like
a
(1)

Report
Copy link

Link copied!

@Valantis Thank you so much for your suggestions.

I tried replacing the "File Content" with each of the following, File ID, File Name, and File Path from the dynamic content and received the following error with each one:

Action 'Copy_file' failed: Failed to verify the existence of source object at 'https://centene.sharepoint.com/teams/BESSContentRepository/Project Upload Form Responses/Project Upload FormBTS Master Services Agreement Welcome.story' due to error 'The system cannot find the file specified. (Exception from HRESULT: 0x80070002)'. clientRequestId: 80630b1c-70c5-447e-917e-879c443ddff1 serviceRequestId: cec70ca2-60d6-1000-9e35-e7b3a2148de0

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @EC-14041929-0,

The error makes sense now. Looking at your screenshot, the "File to Copy" field is pulling the identifier from one of the Create new folder actions, not from your trigger. That's a folder path, not the actual file so SharePoint is looking for something that isn't a file and throws that error.
Open the Copy file action, click into the "File to Copy" field, remove what's there, and open the dynamic content panel. You need to scroll up past all the folder creation steps and find the output from your trigger at the very top the one called "When a file is created in a folder". From there pick Identifier or Path.
That identifier points to the actual uploaded file, which is what the Copy file action needs.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No