{"version":"2.1.228","anchor":"team-file-lock-contention-is-no-longer-counted-as-a-storage-","canonical_anchor":"team-file-lock-contention-is-no-longer-counted-as-a-storage-","heading":"Team-file lock contention is no longer counted as a storage error","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/team-file-lock-contention-is-no-longer-counted-as-a-storage-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Team-file lock contention is no longer counted as a storage error\n\nLosing a lock race on a shared team file is no longer counted as a storage error.\n\n**What**\n\nWhen a teammate team-file update loses a lock race, it is now reported as \"lock_contended\" and the generic failure telemetry is suppressed, so contention stops inflating the storage error count.\n\n**Details**\n\n- Matched on an unavailable result carrying a lock-contended telemetry code, mirroring an existing check for a suspect lock.\n\n**Evidence**\n\n`swarm_team_file_update`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}