{"version":"2.1.251","anchor":"diagnostics-for-tunnels-that-drop-mid-transfer","canonical_anchor":"diagnostics-for-tunnels-that-drop-mid-transfer","heading":"Diagnostics for tunnels that drop mid-transfer","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/diagnostics-for-tunnels-that-drop-mid-transfer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Diagnostics for tunnels that drop mid-transfer\n\nTunnels that drop mid-transfer now log byte counts and say resets are expected.\n\n**What**\n\nConnections tunnelled through the agent proxy that close partway through an exchange now record how many bytes moved, how many were pending and whether the client was paused, and report a debug message. The troubleshooting notes shown to the agent when a proxy tool call fails now explain that resets and RPC failures mid-transfer are expected once a tunnel is up.\n\n**Details**\n\n- Telemetry fires unconditionally on this failure path.\n- The docs point at the recent relay failures list and the proxy status endpoint rather than at retrying.\n\n**Evidence**\n\n`agent_proxy_request_ws_closed_mid_exchange`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}