{"version":"2.1.300","anchor":"hook-execution-gets-a-timeout-bound-abort-signal","canonical_anchor":"hook-execution-gets-a-timeout-bound-abort-signal","heading":"Command hooks can now be stopped by their configured timeout","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hook-execution-gets-a-timeout-bound-abort-signal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Command hooks can now be stopped by their configured timeout\n\nCommand hooks run through this path now stop when their configured `timeout` in seconds runs out\n\n**Unclear.** It is unclear whether this applies to every command hook or only to one particular way of running them.\n\n**What**\n\nA hook is a command you configure to run automatically at certain points. Each hook can have a `timeout` setting, measured in seconds.\n\nBefore, command hooks in this path ran with no timeout of their own and stopped only if the whole operation was cancelled. Now the hook's `timeout` is applied too, so the hook is stopped when either the time runs out or the operation is cancelled.\n\n**Why**\n\nA slow or stuck hook can no longer run past the timeout you set for it here.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}