{"version":"2.1.274","anchor":"memory-backend-listreadcreateupdatedelete-now-share-a-si","canonical_anchor":"memory-backend-listreadcreateupdatedelete-now-share-a-si","heading":"Memory backend list\/read\/create\/update\/delete now share a single 'store not provisioned' status handler","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/memory-backend-listreadcreateupdatedelete-now-share-a-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Memory backend list\/read\/create\/update\/delete now share a single 'store not provisioned' status handler\n\nMemory-storage error handling for 'store not provisioned' and conflicts was consolidated and renamed internally\n\n**What**\n\nThe internal client that talks to the memory-storage backend (used for listing, reading, creating, updating, and deleting memory data) now routes all of these operations through one shared helper that turns HTTP error codes, like 404, into a consistent typed error before any operation-specific handling runs. This replaces duplicated handling that previously existed separately for each operation. The internal error types for \"store not provisioned\" and \"conflict\" were also renamed.\n\n**Why**\n\nThis is an internal cleanup that makes error handling for memory storage more consistent across list, read, create, update, and delete operations, reducing the chance that one operation handles a missing store or a conflict differently from another.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}