{"version":"2.1.311","anchor":"datadog-log-egress-pause-now-also-triggers-on-403-proxy-deni","canonical_anchor":"datadog-log-egress-pause-now-also-triggers-on-403-proxy-deni","heading":"Diagnostic log uploads pause sooner when a proxy blocks them or the host can't be found","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/datadog-log-egress-pause-now-also-triggers-on-403-proxy-deni","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Diagnostic log uploads pause sooner when a proxy blocks them or the host can't be found\n\nClaude Code now pauses sending diagnostic logs to Datadog when a proxy refuses the host or its address can't be looked up\n\n**What**\n\nClaude Code sends diagnostic logs to Datadog, a log collection service. It now pauses those uploads, and drops the logs unsent for a set time, in more cases:\n\n- A proxy (a server your traffic passes through) refuses the Datadog host with a 403 response marked as a proxy error.\n\n- A proxy says the host is not allowed.\n\n- The host's name fails to resolve to an address on a second try.\n\nThe warning shown when this happens is also reworded.\n\n**Why**\n\nIn locked-down or proxied environments, Claude Code stops trying to post logs it can never deliver.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}