{"version":"2.1.246","anchor":"a-failed-plugin-hook-load-no-longer-poisons-later-loads","canonical_anchor":"a-failed-plugin-hook-load-no-longer-poisons-later-loads","heading":"A failed plugin hook load no longer poisons later loads","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-failed-plugin-hook-load-no-longer-poisons-later-loads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A failed plugin hook load no longer poisons later loads\n\nA plugin hook that fails to load no longer keeps failing on every later attempt.\n\n**What**\n\nWhen loading a plugin's hook module throws, the cached registration is cleared before the error is rethrown, so a later attempt starts clean instead of replaying the failure. Hook enablement also gained an admin guard input next to the existing checks for hooks disabled, managed-only and all-disabled.\n\n**Details**\n\n- The admin guard value is part of the fingerprint used to decide when plugin state has changed.\n- Built-in hook notifications are now installed through the worker platform, and the old in-process scanner that inspected plugin hook module source was removed.\n\n**Evidence**\n\n`guardHeldByAdmin: V_t(),`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}