René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Data not loaded after upgrade to 0.9.31 / iii 0.25.0 — state_store.db files present but API/viewer show 0","articleBody":"## Summary\nAfter upgrading to agentmemory 0.9.31 (iii 0.25.0 + state worker 0.22.20), all previously existing data is gone from the API and viewer. The old `.bin` files in `state_store.db` are still present on disk and have non-trivial sizes, but the new engine treats the store as empty.\n\n## Environment\n- **Version before**: ~0.9.27\n- **Version after**: 0.9.31\n- **Engine**: iii 0.25.0 (pinned)\n- **OS**: macOS\n- **Data dir**: `~/.agentmemory`\n- **Backend**: file (default)\n\n## What happened\n1. Ran `agentmemory stop` on the old version.\n2. Upgraded to 0.9.31.\n3. Started the new version.\n4. Viewer (http://localhost:3113), `agentmemory status`, and `GET /agentmemory/status` all show 0 memories, 0 observations, 0 sessions, 0 graph nodes/edges.\n5. Graph-index migration runs but reports `processed: 0`, `total: 0`, `nodes: 0`, `edges: 0`.\n\n## Evidence that data still exists on disk\n`~/.agentmemory/data/state_store.db/` still contains multiple large `.bin` files (e.g. `mem%3Amemories.bin`, `mem%3Aobservations*.bin`, graph-related files). They were not deleted or truncated by the upgrade.\n\nThe new engine is using the correct absolute path (confirmed via status / compose config).\n\n## Relevant status snippet\n```json\n\"graph\": { \"totalNodes\": 0, \"totalEdges\": 0, ... },\n\"graphIndex\": { \"nodes\": 0, \"edges\": 0, \"processed\": 0, \"total\": 0, \"ready\": true },\n\"index\": { \"bm25Documents\": 0, \"memoriesIndexed\": 0, \"observationsIndexed\": 0, \"sessions\": 0 }","author":{"url":"https://github.com/NikEnPrin","@type":"Person","name":"NikEnPrin"},"datePublished":"2026-11-02T09:47:30Z","url":"https://github.com/rohitg00/agentmemory/issues/1652"}