{"version":"2.1.321","anchor":"remote-control-runner-exits-0-when-session-is-no-longer-acti","canonical_anchor":"remote-control-runner-exits-0-when-session-is-no-longer-acti","heading":"Remote-control runners now exit cleanly when their session has ended","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-runner-exits-0-when-session-is-no-longer-acti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote-control runners now exit cleanly when their session has ended\n\nA remote-control runner now exits with success when its session is no longer active, so it is not counted as a failure\n\n**What**\n\nA runner is a process that carries out work for a remote-controlled session. When a runner finds that its session is no longer active, it now exits with code 0, which means success, and says \"the session is no longer active, so this runner is not needed\". When its work order has expired, it still exits with code 1, which means failure. This check also no longer depends on an extra condition, so it applies in more cases.\n\n**Why**\n\nIf you run your own runners, a session that ended normally no longer shows up as a failed run.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}