{"version":"2.1.268","anchor":"sessionstart-hooks-can-be-cut-short-by-an-orphaned-signal","canonical_anchor":"sessionstart-hooks-can-be-cut-short-by-an-orphaned-signal","heading":"SessionStart hooks can be cut short by an 'orphaned' signal","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/sessionstart-hooks-can-be-cut-short-by-an-orphaned-signal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### SessionStart hooks can be cut short by an 'orphaned' signal\n\nSessionStart hooks can now be stopped early if the session becomes orphaned\n\n**What**\n\nThe code that runs `SessionStart` hooks (which fire when a session begins or resumes) now checks for a new `orphaned` signal in addition to the existing abort signal. If either is triggered, the hook run stops early instead of continuing to wait.\n\n**Why**\n\nThis avoids waiting for hook results in a session that has already become orphaned, which is a change from the prior grace-period settling behavior that waited for pending async hooks to finish before continuing.\n\n- Area: Hooks\n- Names: `SessionStart`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}