Recall problems can come from config, content, or expectations.

## Symptoms and fixes

| Symptom | Likely cause | First action |
| --- | --- | --- |
| no candidates | embeddings or views not configured, memory lacks disclosure/glossary | verify setup, then improve the memory |
| wrong candidates | broad memories or inflated priority | split broad notes and lower priority |
| Chinese recall is poor | PostgreSQL fell back to `simple` tokenizer | install `pg_jieba` or `zhparser` |
| recall is slow | too many broad generated views, slow model/db, low timeout | inspect recall analysis and tune limits |
| agent ignores recall | hook not running or agent did not open nodes | verify runtime hooks and usage tracking |

Use the Recall page to compare the prompt, candidate list, scores, and whether nodes were opened.
