{"version":"2.1.242","anchor":"turn-analysis-survives-a-bad-message-and-reports-when-it-deg","canonical_anchor":"turn-analysis-survives-a-bad-message-and-reports-when-it-deg","heading":"Turn analysis survives a bad message and reports when it degraded","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/turn-analysis-survives-a-bad-message-and-reports-when-it-deg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Turn analysis survives a bad message and reports when it degraded\n\nA bad message no longer breaks turn analysis; failures are skipped and reported instead of passing silently.\n\n**What**\n\nThe check for whether a turn was user-driven now catches errors per message and skips the ones that throw. If the whole scan fails it returns a default and emits telemetry `tengu_turn_tail_analysis_degraded`, so the degradation shows up rather than passing silently.\n\n**Evidence**\n\n`tengu_turn_tail_analysis_degraded`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}