{"version":"2.1.227","anchor":"lock-releases-now-log-instead-of-failing-silently","canonical_anchor":"lock-releases-now-log-instead-of-failing-silently","heading":"Lock releases now log instead of failing silently","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/lock-releases-now-log-instead-of-failing-silently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Lock releases now log instead of failing silently\n\nFailed lock releases now log a warning, including when a lock vanished before release.\n\n**What**\n\nReleasing a task or mailbox lock goes through a shared helper that catches the error and logs a labelled warning. It distinguishes a lock that was already gone at release time, noting that the protected section may have run without exclusivity, from a stale lock directory left behind.\n\n**Details**\n\n- Labels identify the call site, such as claiming a task, claiming a task with a busy check, or writing to a named recipient's mailbox.\n\n**Evidence**\n\n`lock was no longer held at release`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}