{"version":"2.1.227","anchor":"lock-release-failures-now-say-what-went-wrong","canonical_anchor":"lock-release-failures-now-say-what-went-wrong","heading":"Lock release failures now say what went wrong","tier":"notice","area":"Error Messages","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/lock-release-failures-now-say-what-went-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Lock release failures now say what went wrong\n\nInternal lock release failures now show a readable explanation instead of a raw error dump.\n\n**What**\n\nWhen Claude Code fails to release an internal lock, it now describes the failure instead of dumping the raw error.\n\n**Details**\n\n- A lock that was already released reports that it was no longer held and that the protected section may have run without exclusivity.\n- Any other failure reports that the lock directory could not be removed and is left to go stale.\n- A release that rejects with something that cannot be described is reported as such rather than throwing inside the error handler.\n\n**Evidence**\n\n`lock directory could not be removed and is left to go stale`\n\n- Area: Error Messages\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}