https://vapi.ai/ logo
Join Discord
Powered by
repeat function calling
# support
h
i have it on async disabled and im sending the request back properly so im not sure what is going on. it keeps saying just a sec then sending to the webhook after it already got a response
v
message has been deleted
@howwy It sounds like you're experiencing an issue with the timing of the webhook responses. If you have asynchronous processing disabled, your system should be waiting for the response before proceeding. However, if it's saying "just a sec" and then sending to the webhook after already receiving a response, there might be a problem with how the responses are being handled or a race condition in your code. To help you better, I would need more specific details about your implementation. Could you provide more information about how you're handling the responses and the sequence of events that leads to the issue? This will help me understand the problem and offer a more accurate solution.
You can continue this conversation by mentioning me in the message.
h
this is how my response is structured: { "results": [ { "toolCallId": "{{1.message.toolCalls[].id}}", "result": "The slot isn't available. These are the availaible slots: {{12.data}}" } ] }
this is how the response is structured: { "results": [ { "toolCallId": "{{1.message.toolCalls[].id}}", "result": "The slot isn't available. These are the availaible slots: {{12.data}}" } ] } so i am using the official way
v
@howwy It seems like you're using the correct format for the response structure, which includes the 
toolCallId
and the 
result
with dynamic data being inserted. If you're encountering an issue where the system is responding with "just a sec" and then triggering the webhook again, it could be due to a few reasons: 1. **Concurrency Issue**: There might be a concurrency issue where the system is not properly waiting for the response before moving on to the next step. 2. **Webhook Configuration**: The webhook might be configured to retry upon receiving a certain response, or it might not be recognizing the response as successful. 3. **Response Handling**: The system might not be correctly handling the response, possibly due to incorrect parsing of the dynamic data or an unexpected format of the received data. To troubleshoot this issue, you can: - **Check the Webhook Configuration**: Ensure that the webhook is set up to handle responses correctly and that there are no retry mechanisms incorrectly triggering. - **Review the Code Logic**: Make sure that the code handling the response is correctly parsing and using the dynamic data. - **Inspect the Logs**: Look at the server logs to see if there are any errors or retries happening that could explain the behavior. - **Test with Static Data**: Temporarily replace the dynamic data with static data to see if the issue persists. This can help isolate whether the problem is with the dynamic data or another part of the system. If after these steps the issue is still not resolved, please provide more details or consider reaching out to the support team for further assistance.
h
@Sahil 🥹
s
call_id pls
h
6784b0f8-341e-4e9e-a89d-7115959621e0
s
Copy code
json

    {
      "role": "user",
      "time": 1719791445415,
      "endTime": 1719791448285,
      "message": "Yes. Can I book an appointment for tomorrow 5 PM?",
      "duration": 4.97,
      "secondsFromStart": 2.96
    },
    {
      "role": "tool_calls",
      "time": 1719791448287,
      "message": "",
      "toolCalls": [
        {
          "id": "call_aYFyeJMD4M8EL6YDnqQ2ZNI4",
          "type": "function",
          "function": {
            "name": "bookingFunc",
            "arguments": "{\n  \"bookingTime\": \"tomorrow at 5pm\",\n  \"clientID\": \"SF4PXBd2WRioFwZ00shz\"\n}"
          }
        }
      ],
      "secondsFromStart": 6.311
    },
    {
      "role": "bot",
      "time": 1719791449975,
      "source": "",
      "endTime": 1719791451465,
      "message": "This will just take a sec.",
      "secondsFromStart": 7.52
    },
    {
      "name": "bookingFunc",
      "role": "tool_call_result",
      "time": 1719791451333,
      "result": "No result returned.",
      "toolCallId": "call_aYFyeJMD4M8EL6YDnqQ2ZNI4",
      "secondsFromStart": 9.357
    },
    {
      "role": "tool_calls",
      "time": 1719791452361,
      "message": "",
      "toolCalls": [
        {
          "id": "call_aYFyeJMD4M8EL6YDnqQ2ZNI4",
          "type": "function",
          "function": {
            "name": "bookingFunc",
            "arguments": "{\n  \"bookingTime\": \"tomorrow at 5pm\",\n  \"clientID\": \"SF4PXBd2WRioFwZ00shz\"\n}"
          }
        }
      ],
      "secondsFromStart": 10.385
    },
    {
      "role": "bot",
      "time": 1719791454265,
      "source": "",
      "endTime": 1719791455285,
      "message": "Hold on a sec.",
      "secondsFromStart": 11.81
    },
    {
      "name": "bookingFunc",
      "role": "tool_call_result",
      "time": 1719791454983,
      "result": "No result returned.",
      "toolCallId": "call_aYFyeJMD4M8EL6YDnqQ2ZNI4",
      "secondsFromStart": 13.007
    }
  ],
@howwy you are not returning the result properly
h
this is what im returning { "results": [ { "result": "The slot isn't available. These are the availaible slots: {{12.data}}", "toolCallId": "{{1.message.toolCalls[].id}}" } ] }
{ "results": [ { "result": "The slot isn't available. These are the availaible slots: {"2024-07-01":{"slots":["2024-07-01T08:00:00-04:00","2024-07-01T09:30:00-04:00","2024-07-01T11:00:00-04:00","2024-07-01T12:30:00-04:00","2024-07-01T14:00:00-04:00","2024-07-01T15:30:00-04:00"]},"2024-07-02":{"slots":["2024-07-02T08:00:00-04:00","2024-07-02T09:30:00-04:00","2024-07-02T11:00:00-04:00","2024-07-02T12:30:00-04:00","2024-07-02T14:00:00-04:00","2024-07-02T15:30:00-04:00","2024-07-02T17:00:00-04:00"]},"traceId":"e316e704-64db-4913-9702-f7d617b8fdcc"}", "toolCallId": "call_aYFyeJMD4M8EL6YDnqQ2ZNI4" } ] }
s
Sent you a meeting link.
Let's debug it over there
h
@Shubham Bajaj @Solv
s
@howwy check dm.
h
Did you manage to fix it?
Even I'm stuck unable to get the result from make.com. Despite using the right format.
h
Using sum else atp
s
create a new ticket please.
2 Views
PreviousNext
Powered by