{"version":"2.1.282","anchor":"detached-cloudremote-runs-report-halted-detached-with-ma","canonical_anchor":"detached-cloudremote-runs-report-halted-detached-with-ma","heading":"Remote runs report when they were detached because the machine stopped","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/detached-cloudremote-runs-report-halted-detached-with-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Remote runs report when they were detached because the machine stopped\n\nA remote run's status can now say it was detached because the machine stopped, instead of only saying it ended\n\n**Unclear.** It is not clear where this status is shown to a user.\n\n**What**\n\nWhen a remote run was detached and did not end normally, its status report now says `halted: \"detached\"` with the cause `machine_stopped`. Before, the only halt reported was `ended`.\n\nThe separate field saying whether an upload was in progress has been dropped from this report.\n\n**Why**\n\nA remote session can now tell a machine that stopped apart from a run that finished.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}