end call fails after another tool call for google ...
# support
r
call id: c14b5237-9700-446e-a72e-ec3cf4877649 I am getting the error
An error occurred in this call: pipeline-error-google-llm-failed
while executing this part of my prompt
Copy code
8. Make the booking using the CreateAppointment with the values provided by the user.  
9. If the booking is successful, politely inform the caller that the booking is complete and indicate the call will now end. End the call using the endCall tool after speaking the end call phrase.
i can see tha the tool call executed succesfully but the call doesn't end with the call phrase
v
Hi there! I see you're having an issue with the
endCall
tool failing after a successful
CreateAppointment
tool call. Based on the error message
pipeline-error-google-llm-failed
, this could be happening for a few reasons: 1. **Quota or Rate Limiting Issues**: Your Google API key might be hitting rate limits, especially if you're making multiple calls in quick succession. [This has been reported by other users](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343704609096601693). 2. **Timing Issues**: The
endCall
function might be called before all necessary prior interactions are complete. [Some users have experienced similar issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336719759965687923). 3. **Message Formatting**: The LLM might be expecting a specific structure that isn't being followed after the tool execution. Here are some troubleshooting steps you can try: - **Check your parameters**: Ensure the
endCall
tool is receiving the correct parameters:
Copy code
json
{
  "callId": "your-call-id",
  "reason": "Appointment booking completed"
}
- **Verify configuration**: Make sure
endCallFunctionEnabled
is set to true in your dashboard configuration. - **Review your prompt**: Try adding a slight delay or additional confirmation step between the
CreateAppointment
success and the
endCall
execution. - **Inspect logs**: Look for any specific error details beyond the general pipeline error. If you continue to experience issues, collecting specific call IDs and detailed error logs would be helpful for further troubleshooting. Sources: - [Discord Thread on pipeline-error-google-llm-failed](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343704609096601693) - [Discord Thread on endCall timing issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336719759965687923)
s
cc-ing @Mason to help you @Raju
k
It looks like the error occurred because the system expected a simple text string, but an object was provided in the
text
field. To resolve this, we need to update the payload so that the
text
field your function is returning contains a string, not an object. Let me know if you'd like help making that change!
We as in it's on your side but we can do it together.
r
@Mason yeah sure, would appreciate your help. what do i need to do to make that change
k
Sure absolutely, you would need to go into the server that your tool is hitting and adjust it to return valid text, not an object. Could you go in and confirm that?