{"version":"2.1.246","anchor":"memory-store-errors-say-available-instead-of-connected","canonical_anchor":"memory-store-errors-say-available-instead-of-connected","heading":"Memory store errors say \"available\" instead of \"connected\"","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/memory-store-errors-say-available-instead-of-connected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Memory store errors say \"available\" instead of \"connected\"\n\nMemory store errors now say no store is available and list the ids you can use.\n\n**What**\n\nThere is no longer a connecting state when resolving a memory store. A session with no store bound says none is available, an unknown store id lists the ids you can use, and a personal id used where a project one is expected is rejected as unknown.\n\n**Details**\n\n- Read-only stores still list the ids you can write to.\n- The resolver returns the store together with its backend instead of building one on the spot.\n\n**Evidence**\n\n`No memory store is available in this session.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}