Storage failed: Request accepted, processing in background

[chinahbcq]

这个系统网上吹爆了，试着部署了一下，运行demo，万里长征路还是第一步，加油，效果不好

📝 Step 1: Store Conversations

ℹ️ Initialized conversation metadata (Scene: assistant)
❌ Storage failed: Request accepted, processing in background
❌ Storage failed: Request accepted, processing in background
📝 Recorded: I love Barcelona the most, Messi is my i... (Waiting for more context to extract memories)
📝 Recorded: I also enjoy watching basketball, NBA is... (Waiting for more context to extract memories)
📝 Recorded: I will sleep now... (Waiting for more context to extract memories)
❌ Storage failed: Request accepted, processing in background
❌ Storage failed: Request accepted, processing in background

⏳ Step 2: Wait for Index Building

💡 Tip: Memory extraction requires sufficient context
- Short conversations may only record messages, not generate memories immediately
- Multi-turn conversations with specific information are easier to extract memories from
- System extracts memories at conversation boundaries (topic changes, time gaps)
⏳ Waiting 10 seconds to ensure data is written...
✅ Index building completed

🔍 Step 3: Search Memories

💬 Query 1: What sports does the user like?
🔍 Found 3 memories (took 0.00ms)

 [1] Relevance: 0.0000 | Time: N/A
     Subject: User Shares Soccer and Basketball Interests, Mentions Idol Messi and Plans Sleep on Feb 25, 2026
     Summary: On February 25, 2026 (Wednesday) at 09:40 AM UTC, the user s...
     Details: On February 25, 2026 (Wednesday) at 09:40 AM UTC, the user stated they love play...

 [2] Relevance: 0.0000 | Time: N/A
     Subject: User Shares Soccer and Basketball Interests, Mentions Idol Messi and Plans Sleep on Feb 25, 2026
     Summary: On February 25, 2026 (Wednesday) at 09:40 AM UTC, the user s...
     Details: On February 25, 2026 (Wednesday) at 09:40 AM UTC, the user stated they love play...

 [3] Relevance: 0.0000 | Time: N/A
     Subject: User Comments on Good Weather During Conversation on February 25, 2026 at 09:40 AM UTC
     Summary: On February 25, 2026 (Wednesday) at 09:40 AM UTC, a conversa...
     Details: On February 25, 2026 (Wednesday) at 09:40 AM UTC, a conversation began in which ...

[JasonOA888]

This "Storage failed: Request accepted, processing in background" message suggests an async processing pattern where the API returns immediately but storage happens asynchronously.

The error is likely a misleading error message - the API returned HTTP 202 (Accepted) which indicates the request was accepted for processing, but the client code is treating this as a failure.

Possible causes:

1. Background worker not running - If using Celery/RQ/task queue, the worker process may not be consuming tasks
2. Queue backlog - Previous tasks are blocking new ones
3. Index building delay - BM25/embedding index creation is slow

Debugging steps:

1. Check if background workers are running:

   # If using Celery
   celery -A your_app inspect active

2. Check queue status:

   redis-cli LLEN your_queue_name

3. Look for actual errors in worker logs, not just the HTTP response

This seems like a deployment/configuration issue rather than a code bug. Can you share your config.json and any worker logs?

[cyfyifanchen]

Closing this as part of the EverOS 1.0 issue triage. This issue references the pre-1.0 API or retired infrastructure such as /api/v1/memories, /api/v3/agentic/*, MongoDB, Elasticsearch, Milvus, Redis, Kafka, longjob, or old memory type names. EverOS 1.0 uses POST /api/v1/memory/{add,flush,search,get} with Markdown + SQLite + LanceDB. Migration notes are tracked in PR #258: #258. If the same behavior still occurs on current main with the 1.0 API, please open a fresh issue with a 1.0 repro.