An API request in my vapi tool call just returned this error. In my server I got an http error 499. The request only took around 5 seconds to return the error, so it's weird to see a timeout after such a short amount of time. Is there a way I can maybe increase the timeout?

{
  "name": "apiRequest-f0533121",
  "role": "tool_call_result",
  "time": 1761273014704,
  "result": "{\n \"message\": \"request to - failed, reason: socket hang up\",\n \"type\": \"system\",\n \"errno\": \"ECONNRESET\",\n \"code\": \"ECONNRESET\",\n \"stack\": \"FetchError: request to -",
  "metadata": {
    "responseHeaders": {}
  },
  "toolCallId": "1826280a",
  "secondsFromStart": 155.44
}

Call ID: 019a140b-0978-7991-bf7d-8e250881992f Timestamp: 2025-10-24T03:27:00

Thanks for sharing the error details. To help you further, could you clarify whether this API request is being made as part of a Vapi tool call, a custom LLM integration, or another workflow type? This will help me point you to the correct timeout configuration or troubleshooting steps. Sources: - [Custom LLM with Vapi Integration – Complete Code](https://docs.vapi.ai/customization/tool-calling-integration) - [Personalization with user information](https://docs.vapi.ai/assistants/personalization) - [Debugging voice agents](https://docs.vapi.ai/debugging)

Hi Pedro Lourenco, If you're experiencing issues with workflows, such as errors or nodes not saving, ensure your configurations align with the latest updates. Here's a checklist based on recent changes: 1. **ApiRequest Node**: Ensure you're using the updated

ApiRequest

node instead of the deprecated

HttpRequest

node. It supports POST requests with customizable headers and asynchronous requests. Details are available [here](https://api.vapi.ai/api#:~:text=ApiRequest). 2. **Retries and Backoff**: Utilize the new backoff and retry strategies to manage failed requests effectively. Configure

maxRetries

and

baseDelaySeconds

within your server configurations for optimal retry handling. 3. **Edge Conditions**: Be sure to define explicit criteria for edge conditions to enhance control and readability in your workflows, such as using the

matches

or

booleanExpression

properties. 4. If you're encountering network issues with API Request tools, verify your network settings and API endpoints to ensure they are correctly configured and accessible. For more details, consider reviewing your configurations against the latest [Vapi API documentation](https://docs.vapi.ai/api-reference/calls/create) and [workflow updates](https://docs.vapi.ai/changelog/2025/5/9).