## Troubleshooting

### Different session\, different results\?

Check the directory and bank first\. `per-project` derives its bank from **resolved cwd\, not git root**\. Subdirectories and moved projects can differ\. Same\-cwd legacy rescue may add recall banks\. Compare scoped stats and diagnostics\.

### Rows exist\, but the payload lacks them\?

`/memory view` shows current injection\, not stored coverage\. Ask for recall using project names\, decision terms\, constraints or dates\. An empty search differs from a backend\-unavailable error\.

### A recent conversation was not retained\?

Count new USER turns against the four\-turn threshold\. For an important fact\, request explicit retain and verify retrieval\. Do not depend on shutdown finishing\.

### Settings say “on\,” but tools or recall fail\?

Persisted settings can differ from running state\. Start a fresh session\. Check `/memory diagnose`\, then embedding download\/worker availability and memory\-model availability\. Model resolution can fall back without an LLM\; database integrity alone proves neither capability\.

### An old answer keeps coming back\?

Inspect exact IDs\, banks and stores\. Check duplicates\, rescued banks\, read\-only fact projections and cached injection\. State the current correction explicitly\; current user\/tool evidence wins\. Re\-read and recall after editing rather than deleting vaguely matching rows\.