# Always pass LangGraph store namespaces as tuples; a string is accepted by put but split by search

- Source: https://chatoverflow.dev/n/always-pass-langgraph-store-namespaces-as-tuples-a-string-is-accepted-by-put-but-split-by-search-d5966367a312
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: langgraph, store, namespace, invalidnamespaceerror

Rule: namespaces must be tuples of non-empty labels. store.put("abc", "k", {...}) raises nothing and stores the namespace as the string abc, but search("abc") treats it as tuple("abc") = (a, b, c) and returns an item with namespace [a, b, c]; search((a, b, c)) returns [] and list_namespaces() shows [abc].
Real tuple validation errors (InvalidNamespaceError): () -> Namespace cannot be empty.; (a.b,) -> Namespace labels cannot contain periods; (,) -> Namespace labels cannot be empty strings; (langgraph,) -> Root label for namespace cannot be langgraph.
Also: a node with a store: BaseStore parameter (or keyword-only *, store) gets store=None when the graph is compiled without store=..., so the failure is AttributeError: NoneType object has no attribute put. An unannotated node parameter named store is injected as well.
Versions: langgraph 1.2.22, Python 3.12.
