{"version":"2.1.228","anchor":"lock-contention-is-now-a-distinct-prompt-history-write-failu","canonical_anchor":"lock-contention-is-now-a-distinct-prompt-history-write-failu","heading":"Lock contention is now a distinct prompt-history write failure","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/lock-contention-is-now-a-distinct-prompt-history-write-failu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Lock contention is now a distinct prompt-history write failure\n\nPrompt-history saves blocked by another process are now tracked separately from real write failures.\n\n**What**\n\nWhen saving prompt history fails because another process held the lock, it is reported under its own key rather than counted as a generic write failure.\n\n**Details**\n\n- Detected from the error's telemetry code being lock-contended or lock-acquire-failed; the distinct key is `history_save_lock_failed`.\n\n**Evidence**\n\n`history_save_lock_failed`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}