I can't figure out why my tool stopped working. Essentially this tool when triggered triggers as make,com scenario to get data from a google sheet. my tool is successfully activating, triggering the webhook and on make.com it says it successfully sending it back out but Vapi is not receiving the data. { "name": "getConstructionStatus", "role": "tool_call_result", "time": 1725844593346, "result": "No result returned.", "toolCallId": "call_rwxCEUVyg7b6sLAZZOVK4zDI", "secondsFromStart": 12.698 } https://cdn.discordapp.com/attachments/1282513556981682348/1282513557144993823/image.png?ex=66dfa153&is=66de4fd3&hm=22ac1dfb32ef7e1b7ddcfd6ac69a1f4cc7c12a7cfc161709d1994ca40d32fe60&

message has been deleted

An example @jason

The toolcallId is there as well, it used to work but when i chagne dthe text in the excel sheet it stopped recieving the data

@Eliminator It's good to hear that you are using the correct response format. Since the issue started after changing the text in the Excel sheet, it's possible that the format or data type of the information being sent to VAPI might have been altered in a way that is not expected by your tool's logic. Here are a few additional steps to consider: 1. **Data Validation**: Double-check the data in the Excel sheet to ensure that it matches the expected format and data types required by your tool. For example, if your tool expects a number and the Excel sheet now contains text in that field, it could cause an issue. 2. **Encoding Issues**: If the text change involved special characters or formatting, it might be causing encoding issues. Ensure that the data is being sent in a plain text format without any unsupported characters. 3. **Test with Static Data**: Try sending a static piece of data that you know worked before to see if the issue is with the data itself or with the transmission process. 4. **Check for Conditional Logic**: If your tool has any conditional logic that processes the data based on its content, ensure that the new text in the Excel sheet still meets those conditions. 5. **Review Changes**: If possible, revert the text in the Excel sheet to the previous state to confirm that the change is indeed the cause of the issue. 6. **Logs and Error Messages**: Check for any new logs or error messages that might have appeared after the change. This could provide clues as to what is going wrong. If you've gone through these steps and the issue persists, it might be helpful to provide a specific example of the data that was changed and the expected versus actual behavior. If you need further assistance, please ask support for more info on this.

@Vapi I just change dthe text in the cell and now it wokrs, how do i figre out what text is breaking the tool?

@Eliminator I'm glad to hear that changing the text in the cell resolved the issue. To figure out what text is breaking the tool, you can perform the following steps: 1. **Incremental Changes**: Start with the text that works and make small, incremental changes towards the text that caused the issue. After each change, test to see if the tool still works. This can help you pinpoint the exact change that causes the problem. 2. **Special Characters**: Look for any special characters, symbols, or punctuation in the text that might not be handled correctly by the tool. These can sometimes cause parsing or encoding issues. 3. **Data Types**: Ensure that the text you're entering matches the expected data type (e.g., string, number, date) and format (e.g., "YYYY-MM-DD" for dates). 4. **Length of Text**: Check if there is a character limit for the text in the cell. Sometimes, exceeding a certain length can cause issues. 5. **Escape Sequences**: If the text includes characters that are used as escape sequences (like backslashes

\

), they may need to be properly escaped or handled. 6. **Encoding**: Verify that the text encoding (e.g., UTF-8) is consistent and supported by the tool. 7. **Conditional Logic**: If your tool has any logic that depends on the content of the text, ensure that the new text does not violate any of those conditions. 8. **Logs and Debugging**: If possible, enable detailed logging or debugging mode for your tool to capture more information about how the text is being processed. By isolating the issue through these steps, you should be able to identify the text or characters that are causing the tool to break. Once identified, you can adjust your tool's logic to handle such cases or ensure that the text entered into the Excel sheet adheres to the required format and constraints.

try sending out response in single line and it will work.

that worked, why does that happen? @User

multi line response get's scattered and then evetually fails.