https://vapi.ai/ logo
Join Discord
Powered by
structured data
# support
g
Hi, I have this structured data configured and I send it to an Elasticsearch but I don't receive the data information. Any ideas? https://cdn.discordapp.com/attachments/1369788841023639572/1369788841300328590/image.png?ex=681d22c5&is=681bd145&hm=24579d334e671688524a2fcd3c7e7f91c9a07cf57b0931d142ce1101e19b22af&
@User @Shubham Bajaj @Sahil
v
I see you're having trouble with structured data not being received by Elasticsearch. The 1-second structured data request timeout might be too short for processing your data. Could you check your Elasticsearch server logs during a data transmission attempt and share any error messages you're seeing? This would help determine if the issue is related to timeout, data formatting, or connection problems. According to the information I found, timeout settings can cause premature termination of requests if they're too short, and there might also be issues with data formatting or property name casing (snake_case vs. camelCase). Sources: - [Troubleshooting issues with sending structured data from Vapi to Elasticsearch](https://discord.com/channels/1211482211119796234/1336456720913797238) - [What is the impact of the structured data request timeout in Vapi when sending data to Elasticsearch?](https://discord.com/channels/1211482211119796234/1325000684231196775) - [How does the Property Name affect sending structured data from Vapi to Elasticsearch?](https://discord.com/channels/1211482211119796234/1341204221826957432)
I see you're having trouble with structured data not being received by Elasticsearch. The 1-second structured data request timeout might be too short for processing your data. Could you check your Elasticsearch server logs during a data transmission attempt and share any error messages you're seeing? This would help determine if the issue is related to timeout, data formatting, or connection problems. According to the information I found, timeout settings can cause premature termination of requests if they're too short, and there might also be issues with data formatting or property name casing (snake_case vs. camelCase). Sources: - [Troubleshooting issues with sending structured data from Vapi to Elasticsearch](https://discord.com/channels/1211482211119796234/1336456720913797238) - [What is the impact of the structured data request timeout in Vapi when sending data to Elasticsearch?](https://discord.com/channels/1211482211119796234/1325000684231196775) - [How does the Property Name affect sending structured data from Vapi to Elasticsearch?](https://discord.com/channels/1211482211119796234/1341204221826957432)
Try increasing your structured data request timeout from 1 second to 20 seconds by updating your configuration:
Copy code
json
"analysisPlan": {
  "structuredDataRequestTimeoutSeconds": 20
}
The 1-second timeout is likely too short for the LLM to process your request, extract the data, and return it in the required format before timing out. Source: - [Troubleshooting steps for when structured data is not received in Elasticsearch from Vapi](https://discord.com/channels/1211482211119796234/1265637856383078461)
Try increasing your structured data request timeout from 1 second to 20 seconds by updating your configuration:
Copy code
json
"analysisPlan": {
  "structuredDataRequestTimeoutSeconds": 20
}
The 1-second timeout is likely too short for the LLM to process your request, extract the data, and return it in the required format before timing out. Source: - [Troubleshooting steps for when structured data is not received in Elasticsearch from Vapi](https://discord.com/channels/1211482211119796234/1265637856383078461)
k
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
PreviousNext
Powered by