{"version":"2.1.242","anchor":"bridge-shutdown-tells-the-server-to-stop-work-earlier","canonical_anchor":"bridge-shutdown-tells-the-server-to-stop-work-earlier","heading":"Bridge shutdown tells the server to stop work earlier","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/bridge-shutdown-tells-the-server-to-stop-work-earlier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Bridge shutdown tells the server to stop work earlier\n\nOn shutdown the bridge asks the server to stop sessions before force-killing them.\n\n**What**\n\nOn shutdown the bridge now asks the server to stop each tracked session before waiting for those sessions to exit, rather than after force-killing them, and awaits the results at the end.\n\n**Details**\n\n- The stop calls carry the current environment secret, including one obtained by re-registration.\n- Failures are labelled for telemetry under `bridge_work_stop`: `env_gone` when the resource is already gone, `shutdown_403` for a 403, `shutdown_failed` otherwise.\n\n**Evidence**\n\n`shutdown_403`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}