{"version":"2.1.246","anchor":"memory-refusals-name-two-more-specific-causes","canonical_anchor":"memory-refusals-name-two-more-specific-causes","heading":"Memory refusals name two more specific causes","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/memory-refusals-name-two-more-specific-causes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Memory refusals name two more specific causes\n\nMemory failures now say invalid_path or not_writable in plain words instead of an HTTP status.\n\n**What**\n\nA memory operation that fails because of a bad path or a store you cannot write to now reports `invalid_path` or `not_writable` in plain words, instead of the generic HTTP status text. The path-prefix hint that says where a store's memories live is now omitted for stores that have no prefix.\n\n**Evidence**\n\n`the store is read-only in this session`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}