function call does not have arguments anymore
# support
h
function call is not outputing arguments anymore
v
Hi there! I understand you're having an issue with function calls not outputting arguments anymore. Let me help you troubleshoot this 🔍 There could be several reasons for this issue based on recent updates and known bugs: ### Possible Causes 1. **Recent API Updates**: There have been enhancements to query parameter handling and changes to the
ToolCall
schema that might affect how arguments are passed and handled [Discord Source](https://discord.com/channels/1211482211119796234/1211483291191083018/1344671338249453660) 2. **UI Configuration Issues**: There's a known bug where settings like headers may appear saved but are lost upon reloading the UI [Discord message](https://discord.com/channels/1211482211119796234/1211483291191083018/1336339138898694184) ### Debugging Steps 1. **Check Tool Call Logic**: - Ensure all parameters and payloads are correctly configured - Verify that your function call format follows the expected structure 2. **Review Response Structure**: - Make sure responses to tool calls follow this format:
Copy code
json
   {
       "results": [
           {
               "toolCallId": "<tool-call-id>",
               "name": "<function-name>",
               "result": "Success" // Or any success message
           }
       ]
   }
3. **Check Logs**: - Look for tool call IDs and responses in your logs to diagnose why arguments aren't being returned 4. **Verify Synchronous vs. Asynchronous Handling**: - If using synchronous calls, be aware that pending results insert a placeholder message - For async calls, there's an issue where they might automatically send success messages to the LLM before completion Let me know if you need more specific guidance based on your implementation! Sources: - [Discord Source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344671338249453660) - [Discord message](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336339138898694184)
k
Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!