call id: 88726a8b-160e-4e98-b834-123db25ab8f8 Time stamp: 03:52 We noticed after setting the idlemessage that it interrupts the tool call (while processing, it says the idlemessage) if the tool call exceeds the idle time set. On the doc it mentions it doesn't interfere so could you look into this issue? It's kind of critical for our release. Another thing is that tool call's ToolMessageDelayed is marked not available for async tool but I think MCP tool calls all counts as async tool call (probably because of MCP calls from a server). Is there an alternative for this ToolMessageDelayed for MCP or async tool calls?

Temporarily disable or extend idleTimeoutSeconds before starting a tool call, then restore it after completion While for async/MCP tools, simulate ToolMessageDelayed by sending a custom “in-progress” message before the tool runs and a follow-up message when it completes..