{"version":"2.1.271","anchor":"hook-chain-failure-logging-now-suppressed-for-expectedabort","canonical_anchor":"hook-chain-failure-logging-now-suppressed-for-expectedabort","heading":"Hook-chain failure logging now suppressed for expected\/aborted errors","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/hook-chain-failure-logging-now-suppressed-for-expectedabort","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Hook-chain failure logging now suppressed for expected\/aborted errors\n\nHook chain failures are no longer logged when the failure is expected or an abort\n\n**What**\n\nPreviously, whenever a chain of hooks (custom scripts that run at certain points in Claude Code) failed, an error was always logged as \"hooks chain failed\". Now that log only appears when a new check determines the failure isn't an expected or aborted case; otherwise it's suppressed.\n\n**Why**\n\nThis cuts down on noisy error logs for hook failures that are expected, such as a hook being intentionally aborted, so the logs better reflect genuine problems.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}