Hey — filing a bug report on query KB tool routing. Assistant: Tim (Copy) — f7aee4ec-6978-4d23-8752-7a7d2abc7f01 Bug 1 — Wrong tool being called: When the assistant should call savings_explanation_knowledge_base_2, it instead calls simple_interest_knowledge_base again with a hidden knowledgeBaseNames argument — even though both tools have empty parameters {}. Returns "No documents found for fileIds." Repro chatIds: d1fe360f-0e55-471b-804e-61e8b5aacb76 245f4706-6f33-460b-8db2-994cfa4cce20 Tools: 56cb1e24 (simple_interest) and fdca31da (savings_explanation_2) Bug 2 — File status inconsistency: All .md files show status: failed via GET /file, yet some still work. All .txt files show status: done but some still fail. The status field appears unreliable. Bug 3 — Files UI missing status: Files UI shows no status or failure reason — only size/type/date/id. Makes KB failures impossible to diagnose without API access. Requests: 1. Fix query tool routing so knowledgeBaseNames isn't injected unless declared in schema 2. Fix/clarify file status reliability 3. Show file status in the Files UI

Yeah this is a tough one the wrong tool firing + unreliable file status makes it really hard to debug properly. Feels like a schema/tool selection issue, so I’d isolate both tools strictly and log the raw payloads to catch where that hidden arg is coming from. For files, I’d ignore status for now and validate via actual retrieval or re-index a small set. I’ve handled similar KB routing issues before, happy to help you sort this out directly. Quick one: are both tools exposed at the same step with equal priority? @lucia

no, not always, I've gone on to test just calling the one tool in the prompt and nothing else and it still returns the no documents found for file ids error message

Ah got it, if it fails even with a single tool, then this points more to a KB indexing/retrieval issue than routing. That error usually means the files aren’t actually retrievable at query time, even if they show as uploaded, so I’d try re-indexing or testing with a fresh file to confirm. Also double check the KB is properly attached to that exact tool instance, not just the assistant. have you been able to get any fileId to return results directly via API? @lucia

well what's strange is that the tool that is working has files that have the status as failed and the files that are status done, when called by a tool, are coming back with the error message. I think the system isn't tagging failed/done statuses correctly on files and also it's mis-calling tools

Hi, is this issue resolved? do let me know if this is still happening