{"version":"2.1.311","anchor":"memory-extraction-handles-abort-separately-and-the-ccr-extr","canonical_anchor":"memory-extraction-handles-abort-separately-and-the-ccr-extr","heading":"Stopped memory saving is no longer reported as a failure","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/memory-extraction-handles-abort-separately-and-the-ccr-extr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Stopped memory saving is no longer reported as a failure\n\nWhen memory extraction is cut short, Claude Code no longer records an error and reports the outcome as unfinished, not failed\n\n**What**\n\nMemory extraction is when Claude Code saves useful facts from a session for later. When an extraction is stopped partway, Claude Code no longer counts that as an error:\n\n- the error report it used to send is skipped\n\n- on one extraction path, the outcome is reported as \"unfinished\" instead of \"failed\"\n\nBefore, any problem, including being stopped, counted as an error and a failure.\n\nRecords of tool calls (actions Claude Code takes, such as reading a file) are now passed to the extractor even when the idle check is off. The server switch for this extraction is off unless it is switched on remotely. The flag server returned off for this site's account and for an anonymous check.\n\n**Why**\n\nEnding a session while memories are being saved no longer produces false failure reports.\n\n- Flag `tengu_passport_quail`: Off in both readings (read for one account on one subscription tier against v2.1.311; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}