{"version":"2.1.260","anchor":"new-taken-back-state-for-stalled-session-liveness-checks","canonical_anchor":"new-taken-back-state-for-stalled-session-liveness-checks","heading":"New 'taken back' state for stalled session liveness checks","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-taken-back-state-for-stalled-session-liveness-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New 'taken back' state for stalled session liveness checks\n\nSession liveness checks gain a distinct taken-back state instead of generic stalled.\n\nSession liveness and probe results gained a `taken_back` variant alongside `stalled`, surfaced as `takenBack: true` on the stalled result. Run and monitor completion messages can now report a task as something other than 'stopped' via a lookup table when it was taken back.\n\n- Area: Sessions\n- Names: `taken_back`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}