SharePoint Document Issues

Fix Power Automate Error: Source Folder Is Already Part of Another Move

Algirdas JasaitisAlgirdas Jasaitis Oct 7, 2026 869 views

Question details

Users encounter an error in Power Automate when trying to move a SharePoint folder, indicating a conflict with another operation.

How to Fix Power Automate Error: Source Folder Is Already Part of Another Move
Product
Microsoft Power Automate / SharePoint
Device & OS
not provided
Scenario
Running an automated flow to move or copy folders across SharePoint directories.
Observed behavior
The Power Automate flow fails with the error message: 'The source folder is already part of another copy or move operation.'
Before you start

Ensure you have access to the Power Automate 'Run history' for the failing flow and adequate SharePoint permissions to view the current status of the target folders.

Solution 1Recommended

Check for Overlapping Flow Runs and Pending Operations

This error most commonly occurs if multiple instances of the flow are running simultaneously or if a manual move operation is still processing in SharePoint.

SharePoint places a temporary lock on a folder while it is being moved or copied. If another flow trigger or a manual user action attempts to move the same folder before the first operation completes, the system rejects it.

1
Verify SharePoint folder status

Navigate to the source document library in SharePoint and check if the folder is visually marked as syncing or if a manual move operation is currently in progress.

2
Review Power Automate run history

Open Power Automate, go to 'My flows,' select the problematic flow, and click on 'Run history'. Check if an earlier run is still marked as 'Running'.

3
Cancel stuck flows

If you find a flow run that is hung or stuck in a loop, click its timestamp and select 'Cancel' from the top menu to clear the operation lock.

4
Wait and retry

Allow a few minutes for SharePoint to completely release the lock on the folder, then manually resubmit the failed flow run to test if the issue is resolved.

Check for Overlapping Flow Runs and Pending Operations
Concurrency Settings: To prevent this issue in the future, consider turning on Concurrency Control in your flow's trigger settings and setting the parallelism degree to 1. This ensures only one folder move processes at a time.
Free Microsoft Office alternative

Streamline Your Office Work with WPS Office

While you troubleshoot complex backend automation issues in SharePoint and Power Automate, you need a dependable suite for your daily document tasks. WPS Office is a highly compatible, free alternative to Microsoft Office that lets you effortlessly view, edit, and collaborate on documents without expensive subscription fees.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the software: Run the installation file and follow the on-screen prompts to set up the suite on your device.
  3. 3. Open Office files seamlessly: Open your exported SharePoint documents directly in WPS Office with zero formatting loss.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight application that launches instantly and consumes minimal system resources.All-in-one tabbed workspace to handle documents, spreadsheets, and presentations together.Built-in PDF editing, converting, and commenting tools at no extra cost.Seamlessly open and edit downloaded SharePoint documents locally.
microsoft office alternative - wps office

Frequently Asked Questions

Why does SharePoint lock a folder during a move operation?

SharePoint temporarily locks the source folder during a move or copy operation to prevent data corruption and ensure data consistency across the server. If another flow or user action attempts to move the locked folder, SharePoint safely rejects it.

How do I limit concurrent runs in Power Automate to prevent folder move errors?

To limit concurrent runs, edit your flow, click the three dots (...) on the trigger action, and select 'Settings'. Toggle 'Concurrency Control' to On, and drag the 'Degree of Parallelism' slider down to 1. This forces flow runs to queue and process sequentially.

Can I use 'Copy file' instead of 'Move file' to avoid this lock?

While copying is generally safer and less prone to strict locking than moving (which involves a deletion step at the source), trying to copy a folder that is already actively being moved or copied by another process can still trigger a similar conflict error.