{"version":"2.1.284","anchor":"hooks-from-a-remote-machine-plugin-fail-cleanly-when-that-ma","canonical_anchor":"hooks-from-a-remote-machine-plugin-fail-cleanly-when-that-ma","heading":"Hooks from a plugin on an unavailable machine now fail with a clear message","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/hooks-from-a-remote-machine-plugin-fail-cleanly-when-that-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Hooks from a plugin on an unavailable machine now fail with a clear message\n\nHooks from a plugin that runs on another machine now report that the machine is unavailable, instead of failing with an unexplained error\n\n**Unclear.** It is not clear what makes a plugin's hooks run on another machine.\n\n**What**\n\nHooks are commands that run at set moments, such as before a tool runs. Some plugins run their hooks on another machine. When that machine is not available, the hook now fails with the message \"This plugin's hooks run on another machine, which is not available.\"\n\n- For events that can block an action, including `PreModelSwitch`, the hook blocks, just as a hook returning exit status 2 would.\n\n- For other events, the hook is treated as having failed to start.\n\n**Why**\n\nYou get an explanation of why the plugin's hooks did not run, instead of an unexplained error.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}