| Previous | Next |
| STATUS_CLOUD_FILE_INCOMPATIBLE_HARDLINKS | STATUS_CLOUD_FILE_REQUEST_CANCELED |
STATUS_CLOUD_FILE_PROPERTY_LOCK_CONFLICT
Another operation owns the placeholder property update
Cloud file metadata can be updated concurrently by the platform, the sync provider, shell integration, and applications. This status means the requested property operation could not obtain a compatible lock. It is a concurrency result, not proof that the property store is corrupt.
The provider must avoid holding property or file locks while making callbacks that can re-enter the same path. A retry can be appropriate after the competing operation completes, but it should be bounded and tied to current file identity because a rename, replacement, or placeholder conversion can make the original request stale.
What to inspect
- Record the file identity, requested property operation, handle access and sharing, thread, and connection key.
- Inspect concurrent provider callbacks, shell property handlers, antivirus filters, and open file handles.
- Check for reentrant provider code that updates properties while already servicing the same item.
- Retry with backoff only after refreshing placeholder state and confirming the item identity is unchanged.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Cloud Files API portal
- Microsoft: CfUpdatePlaceholder
- Microsoft sample: Cloud Mirror
Looking for a different code? Search another status or error code.