{"version":"2.1.277","anchor":"telemetry-failures-in-requestresponse-logging-no-longer-cra","canonical_anchor":"telemetry-failures-in-requestresponse-logging-no-longer-cra","heading":"Telemetry failures in request\/response logging no longer crash the call","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/telemetry-failures-in-requestresponse-logging-no-longer-cra","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Telemetry failures in request\/response logging no longer crash the call\n\nA telemetry failure while logging request or response content no longer crashes the API call\n\n**What**\n\nThe code that computes telemetry about a request's prefix and a response's content is now wrapped in try\/catch. If this telemetry computation fails, Claude Code now logs \"request prefix telemetry failed\" or \"response content telemetry failed\" through its debug logger instead of letting the error propagate and interrupt the API call.\n\n**Why**\n\nPreviously, a bug in this telemetry code could break an otherwise-working API request. Now such a failure is just logged, so telemetry problems can't take down a real request or response.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}