Troubleshooting
Memory and search
Fix Team OS memory import, review, and search problems.
Memory import problems
| Symptom | Likely cause | Fix |
|---|---|---|
| Import is denied | User does not have Full access to the Team. | Use a Full access account or correct the Company or direct Team authority. |
| Client import is denied for a Member | The Member lacks write access to the client. | Grant write client access. |
| Import stays failed | Indexing failed for that source. | Run memory imports --status failed, inspect the error, then retry. |
| Search does not find new content | Import was not indexed, or embedder changed. | Check memory status and keep one embedder per database. |
Run these from command-centre/:
npm run team -- memory imports --status failed
npm run team -- memory retry --id <import-id>For hosted deployments, confirm /v1/health shows the expected embedder.
Memory capture and review problems
| Symptom | Likely cause | Fix |
|---|---|---|
| Capture does not appear in search | Team OS capture is staged first. | Run npm run memory:consolidate, then check Team > Memories. |
| Consolidation sends many items to review | The model found uncertain or sensitive memory. | A Full access user should review and publish only durable items. |
memory:consolidate cannot claim captures | The user is not signed in, or there are no eligible captures yet. | Sign in to Team OS and wait for captures to become eligible. |
| Client capture is denied | The user lacks write access to that client. | Grant write access or capture under a client the user can write. |
| Review controls are missing | The signed-in user does not have Full access to the selected Team. | Select the correct Team and check effective access. |
| Edit or delete controls are missing | The item is not published, or the user lacks Full access. | Open a published memory with a Full access account. |
Pending review items are not searchable. This is expected.
Search access problems
Search uses server-resolved identity. The local workspace can send a narrow scope, but it cannot grant itself access by sending another ID.
| Symptom | Likely cause | Fix |
|---|---|---|
| Search finds a hit, but expand returns no content | The chunk_id was expanded with a different scope, or the chunk is no longer indexed. | Repeat expand with the same scope flags used for search, then check memory status. |
| Transcript drill-down fails in hosted mode | Raw transcripts are local-only in this phase. | Run the transcript command again with --local from the workspace that has context/transcripts/. |
| A client result is missing | The user lacks a client grant, or the request did not include the client layer. | Check the user's client grant and search with the correct --client flag. |
server_embedding_disabled | The request used embeddingMode: "server", but the API was not started with server-side embeddings enabled. | Send queryEmbedding, or restart the API with MEMORY_API_SERVER_EMBEDDINGS=1. |
If a result is missing:
- check whether the memory is
team,client, orprivate; - check the selected Team;
- check Full access or the Member's client grant;
- check whether the source is indexed;
- check whether the request asks for the correct visibility layer;
- check whether the API is connected to the expected database.
For the full search flow, see Layered recall.
Next: Sync troubleshooting