{"version":"2.1.200","anchor":"memory-sync-error-classification-improvements","canonical_anchor":"memory-sync-error-classification-improvements","heading":"Memory Sync Error Classification Improvements","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200\/e\/memory-sync-error-classification-improvements","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200","markdown":"### Memory Sync Error Classification Improvements\n\nThe HTTP error handler for memory operations now parses the server error body and maps specific server error messages to typed error codes:\n\n- `\"memory store has reached its memory limit\"` \u2192 `store_full`\n- `\"content must be at most 102400 bytes\"` \u2192 `content_too_large`\n- `\"memory content appears to contain a credential or API key\"` \u2192 `content_secret`\n- Path validation failures (`\"path must be at most 1024 bytes\"`, `\"path must be NFC-normalized\"`, etc.) \u2192 `invalid_path`\n- `\"cannot modify archived resource\"` \u2192 `store_archived`\n\nUsers will see more specific notifications when memory writes fail for these reasons, rather than generic HTTP error messages.\n\n**Evidence**\n\nError classification map (search for `\"memory store has reached its memory limit\"`, `\"cannot modify archived resource\"`, `\"content must be at most 102400 bytes\"`)"}