{"version":"2.1.300","anchor":"hook-run-on-another-machine-payload-gains-optional-timeout","canonical_anchor":"hook-run-on-another-machine-payload-gains-optional-timeout","heading":"Hooks run on another machine can carry their own time limit","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hook-run-on-another-machine-payload-gains-optional-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hooks run on another machine can carry their own time limit\n\nA hook sent to run on another machine can now include an optional time limit, and its error message no longer says plugin\n\n**What**\n\nA hook is a command you configure to run automatically at certain points in a session. Some hooks can be sent to run on another machine.\n\nThe information sent with such a hook can now include an optional `timeout`, a positive number, alongside the command, its arguments and its JSON input.\n\nThe error logged when this fails now reads \"Hooks: a hook's run on another machine failed\". It no longer says \"a plugin hook's\".\n\n**Why**\n\nHooks run elsewhere can have their own time limit, and the error message now fits hooks that do not come from a plugin.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}