{"version":"2.1.288","anchor":"remote-control-runner-health-server-gets-a-retirestatus-che","canonical_anchor":"remote-control-runner-health-server-gets-a-retirestatus-che","heading":"Remote Control runner health check now tracks retirement and shutdown","tier":"internal","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-control-runner-health-server-gets-a-retirestatus-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote Control runner health check now tracks retirement and shutdown\n\nThe health check of a self-hosted Remote Control runner now polls its token status, including a retire time and whether it is stopping\n\n**Unclear.** What the health check does with the retire time and stopping state is not established.\n\n**What**\n\nA self-hosted runner is a machine you run yourself to host Remote Control sessions, and it can expose a health check that other systems query. That health check now receives a poller for the status of the runner's token, which knows when the runner is due to retire and whether it is shutting down. This only applies when a health port is set.\n\n**Why**\n\nThis is an internal change to how a self-hosted runner reports on itself, so the health check can now tell retirement and shutdown apart from normal running.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}