{"version":"2.1.236","anchor":"disconnect-notice-has-its-own-telemetry-and-opt-out-on-the-r","canonical_anchor":"disconnect-notice-has-its-own-telemetry-and-opt-out-on-the-r","heading":"Disconnect notice has its own telemetry and opt-out on the remote transport","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/disconnect-notice-has-its-own-telemetry-and-opt-out-on-the-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Disconnect notice has its own telemetry and opt-out on the remote transport\n\nThe remote transport can suppress its goodbye notice and lets callers wait for the flush.\n\n**What**\n\nThe remote worker transport's close path sends the disconnect notice, exposes the flush as a promise callers can await, and accepts `{ goodbye: false }` to suppress it. None of this existed in 2.1.235.\n\n**Details**\n\n- Success and failure land under the telemetry name `ccr_worker_goodbye`, with `send_failed` and `send_threw` distinguishing a rejected request from a thrown one.\n- A mid-turn close logs `cli_worker_goodbye_skipped_mid_turn` and sends nothing.\n\n**Evidence**\n\n`\"PUT worker (goodbye)\"`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}