https://dashboard.vapi.ai/calls?callId=019a845a-e5bb-799c-9c89-6afcecc0e624 I see Google GenerateContent error, Anthropic Messages error, and Analysis Summary error. My two questions are (1) what happened here, is this a transient issue (2) how can we retry cases like this? so the caller is not just left hanging

Hi Jessica — thanks for sending the call link and the follow-up questions! The abrupt hang-up happened because the analysis summary request failed, and there was no fallback or error handling configured in your current plan. To prevent this, you’ll want to update your

summaryPlan

to explicitly pass the transcript as a

user

message, with a separate

system

instruction. Right now your config doesn’t provide the transcript in the correct role, so some models will return an error instead of a response, which can end the call. Here’s the format we recommend using (you can copy/paste):

"analysisPlan": {
  "summaryPlan": {
    "enabled": true,
    "timeoutSeconds": 5,
    "messages": [
      {
        "role": "system",
        "content": "You are an expert note-taker. You will be given a transcript of a call. Summarize the call in 2-3 sentences. DO NOT return anything except the summary."
      },
      {
        "role": "user",
        "content": "Here is the transcript:\n\n{{transcript}}\n\n. Here is the ended reason of the call:\n\n{{endedReason}}\n\n"
      }
    ]

hi Kyle, in my view the issue is the agent hanging up at all. the call summary error would've happened after the call ended right? our caller was very shocked to have the agent end the call

It looks like the call ended due to silence timeout after reviewing the recording. The assistant responded to the caller, then heard nothing back for 30 seconds, which triggered the endCall. Also there are some logs that are interesting:

🔵 21:53:08:659 Idle Timeout Triggered But No Idle Message.
🔵 21:53:32:376 [LiveCallPipeline] Silence timed out. Ending call...

we have an idle message configured in the assistant hook, though it doesn't show in the dash. do you know why that no idle message happened? FWIW i hear the "I'm here if you have any questions" all the time https://cdn.discordapp.com/attachments/1439982731420237834/1445809094379438263/Screenshot_2025-12-03_at_11.08.21_AM.png?ex=6931b225&is=693060a5&hm=7c42cfd2e151cdbc29b464ddb1dbc96894d6ebf5d8beb78469a1f87dcac9dd4e& https://cdn.discordapp.com/attachments/1439982731420237834/1445809094903595099/Screenshot_2025-12-03_at_11.08.41_AM.png?ex=6931b226&is=693060a6&hm=3b35fa101ee1121e212a689bea85dddbf960d2b02b5ecb3c8e6ef242df8228ae&

Hi Jessica, Thanks for the follow-up — that clarification helps. The idle message you’re seeing in the dashboard is actually different from the assistant hook–based idle message. The dashboard version used to be the primary method, but assistant hooks are now the most reliable and recommended way to manage idle prompts and fallback behavior. Since you already have an idle hook configured, I’d recommend double-checking the configuration for: - How many times the idle hook is allowed to trigger, and - Whether an endCall tool is set to execute after a certain number of idle triggers (some setups will auto-end the call once the limit is reached). If the assistant is hitting that limit, it could explain why the call terminates even though an idle message exists. Best, Kyle at Vapi Support