Flow failing at sharepoint move copy request

(2) Share

Report

Posted on by Mathieu Laforge

Hi all,

One of my flow that used to work very well now fails in the Sharepoint copy request because of the following error:

"The source folder '<folder name>' is already part of another copy/move operation".

Every execution has failed in the last 3 days.

Any idea how I could reset the folder status?

Thanks in advance,

Mathieu

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi there,

You can try resetting the folder status by following these steps:
1. Go to the site where the file or folder is located.
2. Click on “Site Contents” on the left-hand side of the screen.
3. Click on “Recycle Bin” on the left-hand side of the screen.
4. Find the file or folder that is giving you trouble and click on it.
5. Click on “Restore Selection” at the top of the screen.

This solved the issue for a colleague of mine. I hope it helps you too!

Regards,
Petar Hr.

Was this reply helpful? Yes No
Vrush009 19 on at

Like (0)

Report
Copy link

Link copied!

@MathieuLaforge did you find the solution for this issue? If so, please could you share it as I am facing the same problem.

Was this reply helpful? Yes No
ryanpuffer 35 on at

Like (0)

Report
Copy link

Link copied!

What error are you getting? Currently all of my desktop flows with Sharepoint actions are unable to run.

Was this reply helpful? Yes No
sandeepstw 312 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi There,

It looks like folder you are mentioning is being used in another process. It might happen because some already checked in that file. Please confirm that also you can change it using -
Check the "..." menu next to the folder and select "Manage files which have no checked in version.

Please give kudos and mark as solution if it helps.

Thanks,

Was this reply helpful? Yes No
ryanpuffer 35 on at

Like (0)

Report
Copy link

Link copied!

Just to amend my comment - we ended up having in-house server issues that were causing the issues.

Was this reply helpful? Yes No