API tool response time in the Conversation View
The Conversation View now shows how long your API tools take to respond.
When an API tool is slow, the conversation shows it. A response that takes more than 1 second is marked with the time it took. If several API tools run in one turn, the total appears at the top of that turn. Open a tool’s details to see the time for every response, fast or slow.
Only the time spent waiting for your API is counted. This helps you see when a slow API is behind a slow conversation, and gives your team a clear number to work from.
Who this affects
Every AI Agent that uses API tools. Response times are available for conversations from September 22, 2026 onward. Code tools and MCP tools do not show a response time.
See API tool response time for where each time appears.
ASK steps read every reply and can ask only once
What’s new
ASK steps in structured v2 Playbooks now evaluate the end user’s reply to the last re-ask before the step moves on. The Max re-ask attempts field now accepts 0.
- Every reply is evaluated. Previously, the AI Agent applied the re-ask limit before it read the reply to the last re-ask. The step discarded a valid answer given on the last re-ask and moved on with the fallback value or an empty variable. The Agent now reads that reply first and only then decides whether to move on.
- Max re-ask attempts counts re-asks after the first question. A value of 3 means the Agent asks once and re-asks up to 3 times, 4 questions in total. The default is 3 re-asks, so existing steps ask the same number of times as before.
- Ask only once. Set Max re-ask attempts to 0 and the Agent asks the question once, evaluates the reply, and moves on without re-asking.
Existing ASK steps keep their current settings.
See the ASK step reference for configuration details.