CommunityFind bugs. Earn karma. Help the community.
Sign in to report a bug
Sign InFiles uploaded to an Agent's Knowledge Base are accepted (HTTP 200, success: true), get chunked, sit at status "processing" for 15-20 minutes, then flip to "dead_letter". They never reach "processed", so they never ground the agent. THE PART THAT LOOKS SYSTEMIC Sorting my KB file list by createdAt, every file that has ever reached "processed" was created on or before 2026-06-30. Not one file created after that date has ever succeeded. That is a clean date boundary, not a gradual degradation. TWO API INCONSISTENCIES THAT MAY HELP 1) queue/stats returns "failed": 0 alongside "dead_letter": 6. Items reach the dead-letter queue without ever being counted as failed, so the failure path may not be recorded - which would also explain why nothing surfaces in the UI. 2) The per-file progress endpoint returns status "completed", percentage 100, current_operation "Complete" for files whose record still reads "processing" and which later dead-letter. The two disagree. Queue also shows pending 0 while processing sits at 5 and does not move for 30+ minutes - nothing waiting, nothing advancing, which reads like a stalled worker rather than a backlog. KB totalChunks does increase on upload, so extraction and chunking appear to work; the break looks downstream, at embedding/indexing or whatever marks the record complete. WHAT I RULED OUT - Not size. A 27 KB file fails identically to a 400 KB one. I split large files into five parts under 190 KB specifically to test this; all five failed. - Not type. All plain .txt, and .txt ingested fine before 6/30. - Not content. Same documents that processed successfully in June, in earlier revisions. - Not the upload path. HTTP 200 / success: true, records created with correct byte counts. - Not drag-and-drop user error. Reproduced through the documented API upload endpoint directly. IMPACT This agent is a customer-facing website assistant. The files that cannot be ingested are its primary grounding sources. It sat broken for five weeks with no visible indication. PRODUCT REQUEST Please surface ingestion failures in the UI. A dead-lettered file currently renders identically to a processed one in the Capabilities file list - that is exactly why this went unnoticed. A status badge would have caught it on day one. Account and affected file IDs shared privately with support via chat on 2026-08-03 (Tier 3 lifetime).
I am on AppSumo tier 3 and I can't remove the Tiny Command Branding from form.