[W5UgxTqaij] flexus_vector_search tool call produced by assistant but never executed (no response)

[flexus-teams]

Problem Summary:
Vector search requested by the assistant (flexus_vector_search) never returned a result. The assistant emitted a function-call for flexus_vector_search but there is no corresponding tool response in messages.json and no dispatcher log entry in logs.txt. From the user's perspective: "Vector search is unanswered after 2 mins and a half".

Evidence:

• messages.json (feedback/OuzlpRQFBZ/messages.json) shows the assistant producing a function call for flexus_vector_search:
  {"ftm_role": "assistant", "ftm_num": 28, "ftm_tool_calls": [{"id": "call_39452461", "type": "function", "function": {"name": "flexus_vector_search", "arguments": "{"query":"how do flexus bots work","scope":"internal_docs"}"}}], "ftm_created_ts": 1760694172.741772}
  (See messages.json ftm_num 28 / message_100_? entries.)

• There is no subsequent tool response entry for call_39452461 in messages.json (no tool role entry with that id), and a grep for "flexus_vector_search" in the logs returns no matches:

  • mongo_store grep on messages.json: the assistant emitted the flexus_vector_search call but the tool did not return a result.
  • mongo_store grep on logs.txt: no "vector_search" or call_39452461 entries found.

• By contrast, other function calls are dispatched and logged properly. Example: earlier web/discord calls have explicit local_tool_call log lines in logs.txt, e.g.:

  • 20251017 09:39:14.775 btexe [INFO] SbbassXrSm local_tool_call call_90255421 discord({"op":"help"}) from thread W5UgxTqaij
  • 20251017 09:39:16.625 btexe [INFO] SbbassXrSm local_tool_call call_30275606 discord({"op":"capture","args":{"target":"test-karen","message_id":"1428678710042693652"}}) from thread W5UgxTqaij
    These show the dispatcher logs tool calls; no similar entry exists for call_39452461.

Likely root cause:
The assistant produced a valid-looking flexus_vector_search function-call, but the tool-dispatch layer never executed it (the call appears to have been dropped or not forwarded to the vector-search service). Possible reasons:

• Dispatcher bug: tool-call queued but not processed or dropped silently.
• Missing or misconfigured handler for flexus_vector_search in the runtime that executes tool calls.
• Runtime timed out or rejected the call silently and did not emit an error back to the assistant.

Suggested next steps / mitigation:

1. Check the tool-dispatcher logs/correlation between assistant tool-call ids and local_tool_call entries to see if call_39452461 was received and why it wasn't executed.
2. Add explicit logging when a function-call is accepted, dispatched, completed, or failed (include assistant call id and thread_id) so missing executions are visible.
3. Surface dispatcher/tool execution errors back to the assistant as tool responses (so the assistant can retry or notify the user), instead of silently dropping calls.
4. Verify that flexus_vector_search is registered in the running persona's ft_toolset and that the executor for that function is healthy.
5. Reproduce: send the same query ("how do flexus bots work?") and confirm whether local_tool_call lines for the vector call appear in logs; if not, attach dispatcher logs for the time window around 1760694172.

Attachments / locations:

• feedback/OuzlpRQFBZ/messages.json (assistant tool-call entry ftm_num 28)
• feedback/OuzlpRQFBZ/message_100_18.txt (web tool output earlier)
• feedback/OuzlpRQFBZ/logs.txt (no local_tool_call entry for call_39452461; examples of other tool calls present)

Please triage to the tool-dispatch/runtime team to investigate dropped/missed function-calls for vector search.

@flexus-bob please take a look

[flexus-teams]

I've reviewed the issue details for GitHub #63. This appears to be a runtime/dispatcher problem where the flexus_vector_search tool call is generated by the assistant but not executed (no logs or response). As Bob, my capabilities are limited to code changes in the flexus-client-kit repo via development container and Claude Code for implementation. However, this issue seems to involve the live Flexus system (tool dispatch, vector search service, logging in feedback dirs), which isn't directly fixable through client-kit code changes. The client-kit likely defines tool schemas, but the execution happens server-side. I cannot reproduce or fix the dispatcher without access to the runtime environment. Suggesting this be triaged to the tool-dispatch/runtime team as noted in the issue. No code changes possible here; marking as no actionable steps for client-kit.