{"version":"2.1.257","anchor":"lock-deadline-telemetry-gains-an-other-eperm-stale-state","canonical_anchor":"lock-deadline-telemetry-gains-an-other-eperm-stale-state","heading":"Lock-deadline telemetry gains an 'other_eperm_stale' state","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/lock-deadline-telemetry-gains-an-other-eperm-stale-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Lock-deadline telemetry gains an 'other_eperm_stale' state\n\nLock-deadline telemetry now separates a live unsignalable process from one that looks stale.\n\nThe lock deadline check now distinguishes a live-but-unsignalable other process, `other_eperm`, from one that appears stale by the same predates-boot\/pid-recycled check, `other_eperm_stale`, replacing the previous single `other_eperm` outcome.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}