Move file fails because OneDrive "Database" becomes read only

[Anonymous]

Hey everyone,

we have been using a PowerAutomate flow for about 3-4 months and suddenly (yeah I know: "suddenly" - please bare with me) it creates errors of "the folder is read-only"

The flow is a broken down:

-> When a file is created in folder

-> get information and copy that and create another file

-> move the file that triggered the flow to another folder (archive)

[the "move file" part is done with a recurrance of 2 minutes to prevent the flow from failing due to any restrictions set by MS to the recently opened file - in is generally not possible to have another PA operation with a file that has just been used in a PA flow - after about 7min the file has always been moved]

For some reason that I dont know the flow suddenly went on strike and says that the database is now "read-only".

Things I tried before writing:

- I talked to our IT and they have not changed any attributes for OneDrive

- the same user is able to manually move the file in question into the folder

- the files get a date stamp to prevent any "same file name" issue (but since it happens with multiple files it doesnt matter)

Would someone have an idea as to why this happens or how to prevent that from stoping the flow?

[v-jefferni]

Hi @Anonymous ,

Could you please share more details about your scenario? In a failed run history, which action failed? If it's the move file action, this may be due to the file is pending to synchronize. Sometimes, especially you have quite a lot of files in your OneDrive library, sync could be stuck by one file then this file along with other files pending to sync are locked. Please refer to below doc, try and change sync setting then check if it could help:

Restrictions and limitations in OneDrive and SharePoint - Microsoft Support

Best regards,

[Anonymous]

Thanks for your feedback jefferni,

the flow ran about 10 times a day max - these are all errors and i am unable to look further into the past then 28 days. So i am unable to check a "running" version and a "failed" version.

The trigger is "new file in folder" so the user most likely draged and droped all file in at the same time and then the trigger should run.

While that MAY be an issue it shouldnt be - also there are instances with minutes inbetween or even hours inbetween and the flow still failing at the at the "move file" (last action in the flow - after that is only a recurance to check if the file has been moved).

[v-jefferni]

Hi @Anonymous ,

Since I cannot reproduce this issue, I will only give you some suggestions to have a try:

1. drag and drop only one file a time (from small to big) into this folder and see if the flow will fail.

2. add Delay below the trigger with say 10 minutes to give enough time for the files to create completely and sync successfully.

3. restrict sync files in specific folders as said in previous doc.

Best regards,

[Anonymous]

Thx for the reply - i will try to implement it and hopefully work it out somehow.

[Anonymous · Accepted solution]

So.. old PA wisdow: If a part doesnt work -> Delete it and rewrite it again.

Did so and it works.. Same parameters, same connector, same things around.

No clue why - but i am not complaining anymore