{"version":"2.1.271","anchor":"hook-module-reload-failures-now-recorded-with-generationwan","canonical_anchor":"hook-module-reload-failures-now-recorded-with-generationwan","heading":"Hook module reload failures now recorded with generation\/wanted-text detail","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/hook-module-reload-failures-now-recorded-with-generationwan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Hook module reload failures now recorded with generation\/wanted-text detail\n\nHook module reload failures now log which version and text they expected\n\n**What**\n\nWhen Claude Code's hooks module fails to reload after being flagged as needing an update, it now records more detail about the failure: a generation number, the text that was expected, and the error itself. This gets stored in a map of reload failures that the existing retry logic already relies on.\n\n**Why**\n\nThis gives more diagnostic detail when a hooks configuration fails to reload, making it easier to figure out why a reload attempt failed and what the retry logic saw.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}