{"version":"2.1.248","anchor":"lock-contention-now-tells-the-caller-when-to-retry","canonical_anchor":"lock-contention-now-tells-the-caller-when-to-retry","heading":"Lock contention now tells the caller when to retry","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/lock-contention-now-tells-the-caller-when-to-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Lock contention now tells the caller when to retry\n\nA blocked writer lock now reports a real retry time instead of just a busy marker.\n\n**What**\n\nWhen Claude Code fails to take a writer lock because another process holds it, the result now includes a computed retry time rather than just a \"someone else has it\" marker, so callers can back off to a real timestamp instead of guessing.\n\n**Evidence**\n\n`return { kind: \"other_writer\", retryAtMs:`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}