# Tool Call Output Not Recognized by Agent | Logs Included

**URL:** <https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955>\
**Category:** Support Help\
**Tags:** bug\
**Created:** [March 2, 2026, 9:32pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955 "2026-03-02T21:32:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![NGarcia](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/ngarcia/32/225_2.png) [@NGarcia](https://community.retellai.com/u/NGarcia)\
**Post date:** [March 2, 2026, 9:32pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/1 "2026-03-02T21:32:22Z")

</div>

Hi Retell Team,

I am experiencing an issue where my agent invokes a tool (`Crear_pedido_compra`), the backend processes it successfully, but the agent seems to “ignore” or never receive the tool output. It doesn’t trigger an error; it simply acts as if no response was provided.

**The Issue:**

1. The tool is called at `14:07:11.895`.

2. My internal server logs show the function executed correctly and returned a valid JSON response.

3. Retell logs show a long silence, and then the next latency log appears nearly 3 minutes later (`14:10:10.170`), followed by the call ending.

\*\*Call Logs:  
\*\*  
2026-02-24 14:07:11.895 call\_c41xxxxxxxxxxxxxxxf info: Calling tool: Crear\_pedido\_compra  
Arguments: {“branchId”:“xxx”,“agent”:“xxx”,“clientType”:“xxxxxxxxx”,“execution\_message”:“Estoy creando tu pedido…”,“pse”:true,“phone”:xxxxxxxxxx,“paymentCondition”:“00”,“nit”:“xxxxxxxxxx”,“deliveryType”:“delivery”,“paymentMethod”:“2”,“applyUnloadService”:“2”,“products”:[{“type”:“product”,“id”:xxxxxx,“quantity”:100}]}

2026-02-24 14:07:12.230 call\_c41xxxxxxxxxxxxxxxf info: E2E latency for this turn: 2899  
2026-02-24 14:10:10.170 call\_c41xxxxxxxxxxxxxxxf info: E2E latency for this turn: 3729  
2026-02-24 14:10:21.310 call\_c41xxxxxxxxxxxxxxxf info: Ending call: call\_c41xxxxxxxxxxxxxxxf

**Questions:**

- **Timeout:** Does Retell have a hard timeout for tool responses? My process involves creating a purchase order which might take a few seconds.

- **Response Format:** Is there a specific schema required for the tool output to be correctly parsed by the LLM?

- **Connection:** Why would the dashboard show “no response” instead of a timeout error if the connection was dropped?

Any guidance on why the agent is failing to “see” the tool’s return value would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![support2](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/support2/32/15_2.png) [@support2](https://community.retellai.com/u/support2)\
**Post date:** [March 2, 2026, 9:32pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/2 "2026-03-02T21:32:49Z")

</div>

Based on your logs showing a 3-minute gap between tool invocation and the next latency event, you’re likely hitting a **timeout issue**. The custom function request will timeout in your specified timeout period, or **2 minutes if not specified** [(1)](https://docs.retellai.com/build/conversation-flow/custom-function). When the request fails, it will be retried up to 2 times[(1)](https://docs.retellai.com/build/conversation-flow/custom-function).

## Key Configuration Points

**Timeout Setting:**  
You can configure a custom timeout for your function. The default is 2 minutes (120,000 ms)[(1)](https://docs.retellai.com/build/conversation-flow/custom-function). If your purchase order creation takes longer than this, you need to increase the timeout in your custom function configuration.

**Response Requirements:**  
The response should have a **status code between 200-299** to indicate success[(1)](https://docs.retellai.com/build/conversation-flow/custom-function). The response can be in various formats (string, buffer, JSON object, blob), and all will be converted to string before sending to the LLM[(1)](https://docs.retellai.com/build/conversation-flow/custom-function). The function result is capped at **15,000 characters** to prevent overloading the LLM context window[(1)](https://docs.retellai.com/build/conversation-flow/custom-function).

**Speak After Execution:**  
One common issue is forgetting to enable “Speak After Execution” in your tool configuration. Without this setting, the agent won’t respond after the tool completes[(2)](https://community.retellai.com/t/tool-calling-ai-agent-doesnt-reply-back-stops-interacting/327).

## Troubleshooting Steps

1. **Check your timeout setting** - If your purchase order creation takes more than 2 minutes, configure a longer `timeout_ms` in your custom function[(1)](https://docs.retellai.com/build/conversation-flow/custom-function)

2. **Verify your response format** - Ensure your backend returns a 200-299 status code and the response body is under 15,000 characters[(1)](https://docs.retellai.com/build/conversation-flow/custom-function)

3. **Enable “Speak After Execution”** - This setting ensures the agent continues the conversation after tool execution[(2)](https://community.retellai.com/t/tool-calling-ai-agent-doesnt-reply-back-stops-interacting/327)

4. **Review your prompt** - Make sure your agent prompt explicitly instructs it to continue the interaction after calling tools

For additional support with this specific issue:

- Visit [Documentation](https://docs.retellai.com/general/introduction)
- Ask questions on [Discord](https://discord.com/invite/wxtjkjj2zp)
- Visit [Hire certified Retell partner](https://www.retellai.com/partners)

---

<div class="post-metadata">

**Author:** ![Omar\_Ashraf](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/omar_ashraf/32/102_2.png) [@Omar\_Ashraf](https://community.retellai.com/u/Omar_Ashraf)\
**Post date:** [March 2, 2026, 10:01pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/3 "2026-03-02T22:01:11Z")

</div>

Hello @NGarcia,

Can you share the call ID that has this issue?

---

<div class="post-metadata">

**Author:** ![support2](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/support2/32/15_2.png) [@support2](https://community.retellai.com/u/support2)\
**Post date:** [March 2, 2026, 10:01pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/4 "2026-03-02T22:01:30Z")

</div>

I’m an AI Assistant for Retell AI. It looks like you’re asking someone named NGarcia to share a call ID for an issue. I can help you understand how to retrieve call information using Retell AI’s API.

To get call details, you can use the Get Call API endpoint with a specific call ID[(1)](https://docs.retellai.com/api-references/get-call). The call ID is a unique identifier for each call, formatted as a string (for example: “119c3f8e47135a29e65947eeb34cf12d”)[(1)](https://docs.retellai.com/api-references/get-call).

If you need to investigate a specific issue with a call, having the call ID allows you to retrieve detailed information including call statistics, latency metrics, call analysis, and cost breakdowns[(1)](https://docs.retellai.com/api-references/get-call).

---

<div class="post-metadata">

**Author:** ![NGarcia](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/ngarcia/32/225_2.png) [@NGarcia](https://community.retellai.com/u/NGarcia)\
**Post date:** [March 2, 2026, 10:18pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/5 "2026-03-02T22:18:33Z")

</div>

Yes, it’s the call: call\_c4195bbf84135fbaa0f2efe379f

---

<div class="post-metadata">

**Author:** ![support2](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/support2/32/15_2.png) [@support2](https://community.retellai.com/u/support2)\
**Post date:** [March 2, 2026, 10:18pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/6 "2026-03-02T22:18:58Z")

</div>

I don’t have access to view specific call details or logs for individual call IDs through the documentation sources available to me. To investigate the specific call `call_c4195bbf84135fbaa0f2efe379f`, you’ll need to:

1. **Check the Detail Logs in your Retell Dashboard** - Navigate to your call history and view the detailed logs for this specific call ID to see the exact sequence of events, tool invocations, and any error messages[(1)](https://docs.retellai.com/build/conversation-flow/custom-function)

2. **Verify your custom function configuration** for `Crear_pedido_compra`:

3. **Review the webhook signature verification** - Ensure your server is properly verifying the `X-Retell-Signature` header to confirm requests are coming from Retell[(2)](https://docs.retellai.com/build/single-multi-prompt/custom-function)[(1)](https://docs.retellai.com/build/conversation-flow/custom-function)

4. **Check for retry attempts** - When a request fails, it will be retried up to 2 times[(2)](https://docs.retellai.com/build/single-multi-prompt/custom-function)[(1)](https://docs.retellai.com/build/conversation-flow/custom-function), so look for multiple webhook attempts in your server logs

For direct assistance with investigating this specific call, I recommend:

- Visit [Documentation](https://docs.retellai.com/general/introduction)
- Ask questions on [Discord](https://discord.com/invite/wxtjkjj2zp)
- Visit [Hire certified Retell partner](https://www.retellai.com/partners)

The support team will have access to your call details and can provide specific diagnostics for call ID `call_c4195bbf84135fbaa0f2efe379f`.

---

<div class="post-metadata">

**Author:** ![Omar\_Ashraf](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/omar_ashraf/32/102_2.png) [@Omar\_Ashraf](https://community.retellai.com/u/Omar_Ashraf)\
**Post date:** [March 3, 2026, 8:40pm UTC](https://community.retellai.com/t/tool-call-output-not-recognized-by-agent-logs-included/955/7 "2026-03-03T20:40:49Z")

</div>

Hello @NGarcia

I’ve checked the call, and indeed, your function didn’t return a response.

You can check your server to see how long it took to finish.

As for the timeout, it was 120000 ms.
