{"version":"2.1.260","anchor":"new-session-release-reason-for-max-age-expiry","canonical_anchor":"new-session-release-reason-for-max-age-expiry","heading":"New session-release reason for max-age expiry","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-session-release-reason-for-max-age-expiry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New session-release reason for max-age expiry\n\nSession releases from hitting max age are now tracked as their own outcome.\n\nThe self-hosted runner's session release\/retire state machine gained distinct `released_false_max_age` and `released_false_max_age_parked` outcomes, so a session release triggered by hitting a max-age limit is now tracked separately from the existing shutting-down and retiring outcomes.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}