{"version":"2.1.260","anchor":"new-max-session-age-retirement-path-for-cloudrunner-sessi","canonical_anchor":"new-max-session-age-retirement-path-for-cloudrunner-sessi","heading":"New \"max session age\" retirement path for cloud\/runner sessions","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-max-session-age-retirement-path-for-cloudrunner-sessi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New \"max session age\" retirement path for cloud\/runner sessions\n\nRunner sessions now retire with a distinct max-age reason instead of generic shutdown.\n\nCloud\/runner sessions can now retire with a dedicated \"max-age\" reason (max session age reached), distinct from the existing \"shutdown\" and \"retire\" outcomes, with its own \"max-session-age grace\" period label. The runner's Prometheus metrics now treat a max-session-age release as a clean completion, while hitting the max-lifetime hard cap still counts as an interruption.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}