Menu

Debugging 423 Locked Resource
📰

Debugging 423 Locked Resource

DEV Community: api·Jeff·1 day ago
#XVvOoEYd
#devtoapi#devto#dev#lock#token
Reading 0:00
15s threshold

Quick answer: A 423 Locked means the target resource is currently held under a lock, usually by another client or process, so your write cannot proceed. Find the lock holder and its timeout in the response body, then either wait for release, send the correct lock token if you hold the lock, or ask an administrator to clear a stale lock. Retrying the same request without a change just returns 423 again.

What the status code means

The 423 status comes from WebDAV and describes a resource that is locked. A lock grants one client the right to modify a resource while blocking others, a pattern used in collaborative editing and guarded uploads. The request reaches the right resource and the caller may be authorized, but the lock blocks the write until it is released or the matching token is presented.

This differs from a 409 Conflict. A 409 reports a state mismatch, such as a stale version field, often resolved by re-reading and re-applying.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.