Nextcloud file stays locked: which lock is blocking it?

Locked does not identify the cause

A report for Nextcloud 35.0.2.2 includes Sabre\DAV\Exception\Locked and a DAV lock-validation path. That identifies a relevant part of the failing request, but does not prove that a particular database table contains a stale lock. Q1 Nextcloud describes transactional locking as protection against simultaneous saves, distinct from preventing users from editing a document. Q2

Separate a visible user lock, a DAV lock, a server-side transactional lock and missing write permissions on the underlying storage. Their similar symptoms require different responses.

Investigate one file carefully

1. Preserve its content. Where readable, retain the current server version and any unsaved local version outside synchronisation. Do not immediately replace the file with another copy.
2. Name the failing operation. Is opening, saving, renaming or uploading blocked? Record the path, timestamp, client and complete redacted error. A file with the same name in another directory is not the same test.
3. Check active editing. Ask authorised participants about open Office sessions, WebDAV clients and ongoing synchronisation. Close a known editing session normally and observe whether the lock clears.
4. Correlate the server request. Have the administrator follow the request ID and identify which module reports the lock. A DAV lock error and a storage-permission failure should not receive the same blanket database cleanup.
5. Narrow the comparison. Can the same user create a new test file in the same permitted directory? Is only one file affected, the entire directory, or every user? This separates individual state from sharing rules or a storage problem.

Choose a response for the identified mechanism

A known user lock should be released through the supported interface by an authorised person. For a demonstrated stale server lock, the administrator should inspect the backend and logs relevant to that version. Change filesystem permissions only when their inspection establishes a fault. Disabling transactional locking removes protection without explaining the underlying problem.

After correction, test one save and verify the resulting content from another authorised view. Confirm that the original editing session has not left an unsaved conflicting version before resuming normal collaboration.

Frequently asked questions

Will chmod 777 help?

It does not explain a DAV lock and can unnecessarily broaden access. First identify the layer rejecting the save.

Should I delete every lock record?

Not during active use and without a specific diagnosis. Other files may be legitimately protected. Provide the version, request ID, lock type and a narrowly scoped test case for assistance.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0189 with KAN KAI WORKS.