{"version":"2.1.293","anchor":"hook-results-can-report-ranelsewhere","canonical_anchor":"hook-results-can-report-ranelsewhere","heading":"Backgrounded hook results can now say the hook ran elsewhere","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/hook-results-can-report-ranelsewhere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Backgrounded hook results can now say the hook ran elsewhere\n\nOne way of running hooks now marks a backgrounded result as having run elsewhere\n\n**Unclear.** What this mark changes for someone using hooks is not shown.\n\n**What**\n\nHooks are commands you set up to run automatically at certain points. When a hook is sent to the background, one path for running it now marks its result as having run elsewhere.\n\n**Why**\n\nThis may stop the same hook from being run twice.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}