web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Getting error The file...
Power Automate
Unanswered

Getting error The file is locked for shared use by when updating the file properties

(3) ShareShare
ReportReport
Posted on by 19

Using Microsoft Flow, I am trying to set default value in a metadata column "Column_1" from a sharepoint OOTB "Created By" column whenever a new item created in a document library. Document library has certain content types associated so when I create a new document by choosing a content type, the Office online opens the document in Edit mode. 

 

I am getting below error when I try to update column "Column_1" using "Update file properties" action

 

Error 423: The file <filename.xlsx> is locked for shared use by <email id>. clientRequestId:<xxx> serviceRequestId:<xxx>

 

How can I check the status of the file if locked or not? Any help is much appreciated. 

 

 

 

 

Categories:
I have the same question (0)
  • v-yuazh-msft Profile Picture
    on at

    Hi @neeraj_bharati,

     

    The error message told that the file is locked for shared use so you couldn't run the flow to Update the file properties

    I afraid that there is no any way you could check the status of the file if locked or not currently.

     

    Please check and see if the following article would help in your scenario:

    https://support.microsoft.com/en-sg/help/313472/the-document-is-locked-for-editing-by-another-user-e...

     

    Please make sure the file isn't locked and no anyone have opened the file when you run the flow update file properties.

     

    Best regards,

    Alice

  • neeraj_bharati Profile Picture
    19 on at

    Thanks Alice for your reply. My flow is required to kick off automatically when-ever a new file is created in the documnet library, so I needed a way to check the lock status. Since the file is created using "New" and the selecting a content type, the file gets opened in Edit mode and thus locked at that point of time. The "Update file properties"  was working fine until last friday (June 15th) but not now it is failing with error I mentioned in my original post. Has something changed in "Update file properties"

  • DrewChen Profile Picture
    4 on at

    Hi there,

     

    The same thing happened to me. Up until July 16, 2018, my flow ran with no errors (it does the same thing as described by the original poster neeraj_bharati. Now it also throws "The file [...] is locked for shared use by [user]...". Any ideas? Thanks!

     

    Andrés

  • Ase_Stromsrud Profile Picture
    12 on at

    I have the same problem. I create a document from content type. It opens in the web browser and I can edit the document. The Flow initiates when document is created and in the flow I want to update the properties of the document with a new value. I get the locked by user error.

    When I try to rerun the flow afterwords It works great.

    How can I make this scenario to work?

  • Community Power Platform Member Profile Picture
    on at

    I'm in the same scenario, I've tried creating a big nasty do-after sequence that loops if it cna't update the file because of lock, never seems to work consistently because it bugs the file out to where it doesn't unlock for like 24hours, cannot find a legitimate way to make document approvals work if it has to update a column on the document.

  • Community Power Platform Member Profile Picture
    on at

    Hello, I get this same error on my flows and it comes up over 50% of the time making Flow unusable.

     

    I need to be able to update columns and sometimes move files as a part of our flows and this "file is locked for shared use" causes the flow to fail at any update file properties or copy file step.

     

    Are there any ways to solve this error or work around it? 

     

    Also, is there a way to set up a loop to keep trying until the file unlocks it self?

     

    Thanks!

    Silvana

  • Community Power Platform Member Profile Picture
    on at

    I'm getting this same issue when updating a file. 

    Still looking for a workaround

  • Alvarocarmona Profile Picture
    18 on at

    Same problem to me. I have a flow working every hour. The process is like this:

    1 New mail with excel arrives.

    2 Take the file and create a new file in one drive with attach content. Same target file every run to update the file.

    3 Create table for this file

    4 Get Rows 

    5 Update rows in PBI Streaming report

     

    It gets stucked because the file is locked when I try to get the rows (4 step) at first run. The next Run (1 hour later) it gets stucked at create File (2 step). The next one again at step 4....

     

    How can be the file locked for more than 1 hour!!

  • efialttes Profile Picture
    14,756 on at

    Hi @Alvarocarmona

    I guess everytime you create a new excel file you reuse the same fileName ('same target file') in order to get the Excel actions work, right?

    If so, I am experiencing the same problem in Sharepoint.

  • apples Profile Picture
    11 on at

    @v-yuazh-msft wrote:

    Hi @neeraj_bharati,

     

    The error message told that the file is locked for shared use so you couldn't run the flow to Update the file properties

    I afraid that there is no any way you could check the status of the file if locked or not currently.

     

    Please check and see if the following article would help in your scenario:

    https://support.microsoft.com/en-sg/help/313472/the-document-is-locked-for-editing-by-another-user-e...

     

    Please make sure the file isn't locked and no anyone have opened the file when you run the flow update file properties.

     

    Best regards,

    Alice



    Thanks for the suggested article. We have the same issues where Flow cannot update meta data associated with the review process if anyone happens to have the document open in their browser.

     

    Is there any other solution/workaround where we can check if the document is locked at all before we trigger the flow. Run_History___Microsoft_Flow.jpg

     

    We purposely disabled checkout so people can co-author documents but this is now causing huge problem within the business.

     

    Thanks

    Aegir

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 538 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 405 Moderator

#3
abm abm Profile Picture

abm abm 252 Most Valuable Professional

Last 30 days Overall leaderboard