I have an agent and it;s not calling the tool no matter what I do, what is the issue? There used to be logs to show things as they happened but now I can't see them. Here is the call id: 2c330b23-5e6e-47b3-8042-b8bed1c8b7c0 Thanks so much! @Shubham Bajaj thanks!

Hi there! 👋 I understand how frustrating it can be when your agent isn't calling a tool and you can't see the logs to troubleshoot. I'm unable to directly access your specific call logs using the ID you provided, but I can definitely help with general troubleshooting steps for both issues you're experiencing. ## Why Your Agent Might Not Be Calling the Tool There are several possible reasons why your Vapi agent isn't calling the tool: ### Configuration Issues According to the [troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334114042876264518) I found, configuration issues within your VAPI setup can prevent tools from being automatically called. This could include: - Incorrect tool configuration - The tool not being configured to trigger under the right conditions - Server-side issues with processing HTTP requests ### Response Format Problems The JSON response format might be incorrect. The tool call response should be a string without line breaks, and JSON responses need to be stringified according to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342315282198298729). Make sure your response follows this format:

json
{
  "results": [
    {
      "toolCallId": "<your-tool-call-id>",
      "name": "<your-function-name>",
      "result": "Success" // Or any success message
    }
  ]
}

### Synchronous vs Async Settings Check if your tool is set to

synchronous

instead of

async

as mentioned in [this discussion](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342315282198298729). ## Troubleshooting Missing Logs As for your logs not being visible anymore, here are some potential reasons: ### Dashboard or Temporary Glitch

Hey Titus, could you share the call ID for which it was working previously so I could compare what's the difference and what would've gone wrong for this shared call ID?

Do you see any issues with the current call I’d

I don't see any issue with the call ID shared. It's most likely to me that it was a prompt or could be one of the cases where LaM is not working as it was supposed to be. Still, if a call ID where it was working as expected would help me potentially find out any discrepancies if any.

@Shubham Bajaj is there a way to pass the current call transcript to a tool?

The payload contains the call object, which contains the transcript.

I mean during the call not the end of call report @Shubham Bajaj for example...

Yes, you get the transcript during this server message of type tool calls inside artifacts. You can use artifacts to get the current call transcript. However, we don't pass the transcript as an argument to the tool call. You get the transcript from artifacts, so we don't need to include it in the tool call arguments.

awesome i found it thanks!!

Marking this ticket as Solved ✅

yes

Marking this ticket as Solved ✅