{"version":"2.1.267","anchor":"reactive-compaction-failures-now-report-a-structured-error-k","canonical_anchor":"reactive-compaction-failures-now-report-a-structured-error-k","heading":"Reactive compaction telemetry gains error-kind and cache-cold fields","tier":"internal","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/reactive-compaction-failures-now-report-a-structured-error-k","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Reactive compaction telemetry gains error-kind and cache-cold fields\n\nReactive compaction now reports a structured error kind and whether the prompt cache was cold when it ran\n\n**Unclear.** The `tengu_reactive_compact_failed` gate hasn't been read for this site's account, so nothing can be said about whether it's active here.\n\n**What**\n\n- Reactive-compaction failure results now include a structured `errorKind` field (`thrown`, `no_assistant_message`, `empty_summary`, or the API's own error tag) alongside the existing free-text detail.\n\n- The reactive-compaction telemetry event now also reports `cacheCold` (whether the prompt cache was cold) and a `status` field, threaded through as a new `cacheCold` option.\n\n**Why**\n\nThis makes it easier to tell why an automatic (reactive) compaction attempt failed and whether a cold prompt cache played a role, improving diagnosis of compaction issues.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}