{"version":"2.1.260","anchor":"self-hosted-runner-now-distinguishes-idle-release-at-max-ses","canonical_anchor":"self-hosted-runner-now-distinguishes-idle-release-at-max-ses","heading":"Self-hosted runner now distinguishes idle-release at max session age","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/self-hosted-runner-now-distinguishes-idle-release-at-max-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Self-hosted runner now distinguishes idle-release at max session age\n\nRunner sessions released for hitting max age now get their own telemetry tag.\n\nSelf-hosted runner sessions released for hitting the maximum session age are now logged and tagged in telemetry as `released_false_max_age`, instead of being lumped in with plain idle releases under the generic `released_false`.\n\n- Area: Self-Hosted Runner\n- Names: `released_false_max_age`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}