{"version":"2.1.302","anchor":"structured-output-refusal-telemetry-and-projects-reply-gate","canonical_anchor":"structured-output-refusal-telemetry-and-projects-reply-gate","heading":"Diagnostic records for dropped structured output and project reply errors","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/structured-output-refusal-telemetry-and-projects-reply-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Diagnostic records for dropped structured output and project reply errors\n\nClaude Code now records when a successful result follows dropped structured output, and when a project reply turn errors\n\n**What**\n\nStructured output is when Claude Code is asked to return its answer in a fixed format. Claude Code now records a usage event when it returns a successful result after that structured output was dropped.\n\nIt also records a diagnostic entry when a turn ends in an error while replying through the projects connection.\n\n**Why**\n\nThese are diagnostic records and do not change what you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}