Repository navigation
Memory Tree stuck with 165 failed pipeline jobs — Gmail 155 pending chunks not processing, Sync button has no effect #3091
Description
User connected multiple accounts on the free plan, which immediately consumed their $1 free credit. They then upgraded to the Basic Plan. Despite upgrading, the Memory Tree is stuck in an error state.
Memory Tree status (from screenshot)
Status: Error — 165 failed job(s) in pipeline
Last Sync: 20 min ago
Total Chunks: 349 | Wiki Size: 113.6 KiB
Gmail: Idle — 346 chunks, last chunk 20m ago, 155 pending
The failed job count and pending Gmail chunks are not decreasing across multiple 20-minute heartbeat cycles. Clicking the Sync button repeatedly has no effect. Auto-sync is enabled.
The pipeline appears stalled — jobs are queued but not being processed. Possible causes: credit exhaustion blocking job execution even after upgrade, a pipeline worker failure, or a state sync issue between the free→paid plan transition. User is unable to use the memory feature as intended.
Discord handle not confirmed — ticket submitted via screenshot + text description only.
Reported by: dejjem
Discord ticket: https://discord.com/channels/1470856511193616498/1510392667106836572
Priority: high
Attachments (1): image.webp — ask support team for files
Activity
senamakel commentedon Jun 1, 2026
resolved in the next build.
oxoxDev commentedon Jun 3, 2026
Resolved on
main— closing per @senamakel's "resolved in the next build" note. Every symptom is addressed across three merged PRs:readyon any sync) + per-source sync mutex → fixes stuck failed-job count and the no-op Sync button. Also adds graceful embedding degradation so Voyage 429 rate limits log-and-continue instead of failing jobs → unblocks the pending Gmail chunks.memory_tree_retry_failedRPC + requeue-on-sync, memory-doctor diagnostic, and honestdegraded/first_blocking_causestatus so a stalled pipeline reports why.Fixes are live on
main; the next build clears this. Please reopen if it recurs after updating.