{"version":"2.1.312","anchor":"datadog-log-egress-refusal-check-refactored","canonical_anchor":"datadog-log-egress-refusal-check-refactored","heading":"Check for blocked Datadog log uploads now records the block as confirmed","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/datadog-log-egress-refusal-check-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Check for blocked Datadog log uploads now records the block as confirmed\n\nWhen the network refuses Claude Code's Datadog log uploads, Claude Code now also records that refusal as confirmed\n\n**What**\n\nClaude Code can check whether the network refuses its log uploads to Datadog, a logging service, and pause sending logs if so. That check, a name lookup, has moved into its own helper. Before, it ran in place with a one-second timeout and a single try. When the check finds the uploads are refused, Claude Code now also marks the refusal as confirmed.\n\n**Why**\n\nThis is a small change to how Claude Code decides to pause sending logs when they are being blocked.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}