How to Fix Power Automate File Trigger Failures When a SharePoint File Is Locked
Question details
The user needs to resolve a Power Automate flow failure where a 'When a file is created or modified (properties only)' trigger runs, but the subsequent 'Update file properties' action fails because the SharePoint file has an exclusive lock while it is still open.
- Product
- Microsoft Power Automate and SharePoint Online
- Device & OS
- not provided
- Scenario
- A Power Automate flow is configured to trigger when a SharePoint file is created or modified, and it then updates file properties while the document may still be open.
- Observed behavior
- The flow reaches 'Update file properties' but fails because the file is exclusively locked; the trigger itself may run, but metadata updates fail until the file is closed or the lock is released.
Before troubleshooting, open the flow run history in Power Automate to confirm which action failed, and check whether the SharePoint document is currently open or checked out in Microsoft 365.
Close the SharePoint File and Release the Lock Before Updating Properties
Use this when the flow fails on 'Update file properties' and the file is still open or checked out; releasing the lock often lets the next run succeed.
Power Automate triggers can fire while a file is open, but metadata write actions require an exclusive lock. The simplest fix is to remove the lock before the update step runs.
Open the SharePoint document library, select the file that failed in the flow run history, and check the file status or 'Checked out' column.
Ask the user to close the file in the desktop or web Office app, or select the file in SharePoint and choose 'Discard check-out' or 'Check in' to release the lock.
Return to Power Automate, open the failed run, and select 'Resubmit' or wait for the next file modification trigger, then confirm 'Update file properties' completes.
Add Retry and Delay Handling to the Power Automate Update File Properties Action
Use this when users may keep the file open for a while; retry or delay logic gives the lock time to be released before the metadata update is retried.
Avoid SharePoint Lock Workflow Headaches with Free WPS Office Editing
When Microsoft 365 workflows fail because a file is locked or checked out, WPS Office gives you a free, lightweight way to create and edit Office documents with familiar formatting, strong Microsoft Office compatibility, and an easy interface that reduces document handoff friction.
Frequently Asked Questions
Can the Power Automate trigger run while a SharePoint file is locked?
Yes. The 'When a file is created or modified (properties only)' trigger often runs even if the file is open or locked. The failure usually occurs later when an action such as 'Update file properties' tries to write metadata and hits the exclusive lock.
How do I release a SharePoint file lock so Power Automate can update properties?
In the SharePoint document library, select the file, then use 'Check in' or 'Discard check-out' if it is checked out. If it is open in a desktop Office app, close it. You can also wait briefly and retry the flow from Power Automate run history.
Why does 'Update file properties' fail but the trigger succeeds?
The trigger can read the file event without needing an exclusive lock, but updating metadata requires write access. If an Office app or SharePoint check-out holds the file lock, the update action fails until the lock is released.
Should I fix this in SharePoint or Power Automate?
This is a Power Automate flow behavior rather than a SharePoint built-in feature. Check the flow run history to confirm the failing action, then either release the lock or add retry/delay handling to the flow.
Will WPS Office prevent SharePoint or Power Automate file lock errors?
WPS Office is not a Power Automate repair tool, but it offers a free, lightweight Microsoft Office alternative for editing and saving .docx, .xlsx, and .pptx files, which can simplify document workflow and reduce Office application dependency.
