{"version":"2.1.232","anchor":"remote-input-dropped-after-a-stream-closes-is-now-reported","canonical_anchor":"remote-input-dropped-after-a-stream-closes-is-now-reported","heading":"Remote input dropped after a stream closes is now reported","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-input-dropped-after-a-stream-closes-is-now-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote input dropped after a stream closes is now reported\n\nRemote input silently thrown away after a stream closes is now reported once per lane.\n\n**What**\n\nWriting inbound data to a closed or destroyed remote input stream used to be silently discarded; it now emits `cli_remote_io_inbound_dropped_after_close` with the affected lane, once per lane per session.\n\n**Evidence**\n\n`cli_remote_io_inbound_dropped_after_close`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}