{"version":"2.1.225","anchor":"classifier-failure-telemetry-gained-a-stopreason-field","canonical_anchor":"classifier-failure-telemetry-gained-a-stopreason-field","heading":"Classifier failure telemetry gained a stopReason field","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/classifier-failure-telemetry-gained-a-stopreason-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Classifier failure telemetry gained a stopReason field\n\nFailure reports for the classifier now include why generation stopped.\n\n**What**\n\nClassifier failure events now report why generation stopped.\n\n**Details**\n\n- `stopReason` is added to the payload alongside `classifierModel`, `classifierType` and `failureKind`\n- the optional `errorKind` and `fallbackFrom` fields are unchanged\n\n**Evidence**\n\n`stopReason`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}